From HeinerHummel@aol.com Sat May 2 15:03:17 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF7293A67A4 for ; Sat, 2 May 2009 15:03:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.097 X-Spam-Level: X-Spam-Status: No, score=0.097 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_50=0.001, HTML_MESSAGE=0.001] 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 dvBb5yQYKYXM for ; Sat, 2 May 2009 15:03:17 -0700 (PDT) Received: from imr-m08.mx.aol.com (imr-m08.mx.aol.com [64.12.138.210]) by core3.amsl.com (Postfix) with ESMTP id D94A93A6CAF for ; Sat, 2 May 2009 15:03:16 -0700 (PDT) Received: from imo-da03.mx.aol.com (imo-da03.mx.aol.com [205.188.169.201]) by imr-m08.mx.aol.com (v107.10) with ESMTP id RELAYIN1-249fcc36f27e; Sat, 02 May 2009 18:04:31 -0400 Received: from HeinerHummel@aol.com by imo-da03.mx.aol.com (mail_out_v40_r1.5.) id z.c35.589c5698 (14467); Sat, 2 May 2009 18:04:25 -0400 (EDT) From: HeinerHummel@aol.com Message-ID: Date: Sat, 2 May 2009 18:04:25 EDT To: tme@americafree.tv, bortzmeyer@nic.fr MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1241301865" X-Mailer: 9.0 SE for Windows sub 5021 X-AOL-IP: 205.188.169.201 Cc: rrg@irtf.org Subject: Re: [rrg] The Pouzin Society X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 May 2009 22:03:17 -0000 -------------------------------1241301865 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable In einer eMail vom 30.04.2009 17:05:29 Westeurop=E4ische Normalzeit schrei= bt tme@americafree.tv: > The Pouzin Society's purpose is to provide a forum for developing > viable solutions to the current Internet architecture > crisis. Interesting. Would this society be interesting in making the Moore's law= applicable to internet routing ? And also in eliminating the BGP-update churn resp. in the reduction of the= Routing table sizes? Would it also be interesting in technological progress wrt. routing ? Like state-less Multicast for 99,9 % of all involved routers? Heiner ---------------------------------- Be assured: P =3D NP ! -------------------------------1241301865 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
In einer eMail vom 30.04.2009 17:05:29 Westeurop=E4ische Normalzeit= schreibt tme@americafree.tv:
> The Pouzin Society's purpose is to provide a forum for developing
> vi= able solutions to the current Internet architecture
> crisis.
Interesting. Would this society be interesting in making the Moore's= law applicable to internet routing ?
And also in eliminating the BGP-update churn resp. in the reduction= of the Routing table sizes?
 
Would it also be interesting in technological progress wrt. routing= ?
Like state-less Multicast for 99,9 % of all involved routers?
Heiner
----------------------------------
Be assured: P =3D NP !
 
-------------------------------1241301865-- From irtf@tonistoev.info Tue May 5 02:34:19 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EFC4D3A7160 for ; Tue, 5 May 2009 02:34:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.954 X-Spam-Level: X-Spam-Status: No, score=-1.954 tagged_above=-999 required=5 tests=[AWL=0.645, 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 HcvUVpv0FV1x for ; Tue, 5 May 2009 02:34:19 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 2185D3A7159 for ; Tue, 5 May 2009 02:34:19 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M1H3v-0004DI-5w for rrg@irtf.org; Tue, 05 May 2009 12:35:43 +0300 From: Toni Stoev Date: Tue, 5 May 2009 12:35:41 +0300 User-Agent: KMail/1.9.9 MIME-Version: 1.0 Content-Disposition: inline To: IRTF RRG Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200905051235.41286.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 09:34:20 -0000 Intra-domain routing can be considered as a general solution. This general solution is the provision of reachability throughout an autonomous system. Node locators can be considered intra-domain locators. Every locator shall have default association with its containing autonomous system in order to be universally recognizable. Utilizing these approaches inter-domain routing can be separated from intra-domain routing. Inter-domain routing shall be based on autonomous system paths and not on IP addresses and prefixes. Thus inter-domain routing tables will be substantially unloaded and more easily managed. This will provide significant improvement to inter-domain routing scalability. From irtf@tonistoev.info Tue May 5 16:34:31 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1109F3A6B25 for ; Tue, 5 May 2009 16:34:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[AWL=0.599, 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 o5g-nmdk3RuQ for ; Tue, 5 May 2009 16:34:30 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 2E7963A69FD for ; Tue, 5 May 2009 16:34:29 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M1UAz-0004ZY-69 for rrg@irtf.org; Wed, 06 May 2009 02:35:53 +0300 From: Toni Stoev To: IRTF RRG Date: Wed, 6 May 2009 02:35:52 +0300 User-Agent: KMail/1.9.9 References: <200905051235.41286.irtf@tonistoev.info> In-Reply-To: <200905051235.41286.irtf@tonistoev.info> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905060235.52415.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 23:34:31 -0000 How can locator have default association with its containing autonomous system? Easy. Autonomous system number shall be incorporated into locator. Universally recognizable locator shall start with it. On Tuesday 5 May 2009 12:35:41 Toni Stoev sent: > Intra-domain routing can be considered as a general solution. This general solution is the provision of reachability throughout an autonomous system. > Node locators can be considered intra-domain locators. Every locator shall have default association with its containing autonomous system in order to be universally recognizable. > Utilizing these approaches inter-domain routing can be separated from intra-domain routing. Inter-domain routing shall be based on autonomous system paths and not on IP addresses and prefixes. Thus inter-domain routing tables will be substantially unloaded and more easily managed. > This will provide significant improvement to inter-domain routing scalability. > _______________________________________________ > rrg mailing list > rrg@irtf.org > http://www.irtf.org/mailman/listinfo/rrg > From robert@raszuk.net Wed May 6 00:58:16 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 44E9C28C2C0 for ; Wed, 6 May 2009 00:58:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.691 X-Spam-Level: X-Spam-Status: No, score=-1.691 tagged_above=-999 required=5 tests=[AWL=-0.735, BAYES_00=-2.599, RCVD_IN_NJABL_PROXY=1.643] 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 nuCwhkOmIary for ; Wed, 6 May 2009 00:58:15 -0700 (PDT) Received: from mail37.opentransfer.com (mail37.opentransfer.com [76.162.254.37]) by core3.amsl.com (Postfix) with SMTP id 4B7383A6DBE for ; Wed, 6 May 2009 00:55:54 -0700 (PDT) Received: (qmail 15899 invoked by uid 399); 6 May 2009 07:57:20 -0000 Received: from unknown (HELO ?192.168.1.53?) (83.24.27.106) by mail37.opentransfer.com with SMTP; 6 May 2009 07:57:20 -0000 Message-ID: <4A0142DE.7040007@raszuk.net> Date: Wed, 06 May 2009 00:57:18 -0700 From: Robert Raszuk User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Toni Stoev References: <200905051235.41286.irtf@tonistoev.info> <200905060235.52415.irtf@tonistoev.info> In-Reply-To: <200905060235.52415.irtf@tonistoev.info> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: IRTF RRG Subject: Re: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: robert@raszuk.net List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 07:58:16 -0000 Hi Toni, Just FYI I and Enke Chen have discussed in the past an algorithmic way to convert 4 byte AS number into the locator. Naturally such locator would be an anycast and one could most likely enter given AS via any peering ASBR. The scheme is very simple. We take 4 byte AS number, assume that we will use 3 last octets while first octet would be all zeros and do normal byte by byte bin to dec conversion. The resulting special IPv4 address would be 0.A.B.C. For IPv6 this is even simpler :). At that time some folks voiced their opinion that making AS part of a locator is a bad thing. Along the same lines they were against tunneling to AS/IP address. Perhaps those folks could comment now why this is a bad choice ? I never understood why we can not make first baby step and introduce some of the hierarchy just by doing this. We pretty much already know today the originator AS from AS_PATH (AS SET is sporadic) as well as number of potentially injected new entires equal to number of ASes would be noise for current BGP. Cheers, R. > How can locator have default association with its containing autonomous system? > Easy. Autonomous system number shall be incorporated into locator. Universally recognizable locator shall start with it. > > On Tuesday 5 May 2009 12:35:41 Toni Stoev sent: >> Intra-domain routing can be considered as a general solution. This general solution is the provision of reachability throughout an autonomous system. >> Node locators can be considered intra-domain locators. Every locator shall have default association with its containing autonomous system in order to be universally recognizable. >> Utilizing these approaches inter-domain routing can be separated from intra-domain routing. Inter-domain routing shall be based on autonomous system paths and not on IP addresses and prefixes. Thus inter-domain routing tables will be substantially unloaded and more easily managed. >> This will provide significant improvement to inter-domain routing scalability. From xuxh@huawei.com Wed May 6 02:21:42 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FD6D3A6868 for ; Wed, 6 May 2009 02:21:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.798 X-Spam-Level: X-Spam-Status: No, score=0.798 tagged_above=-999 required=5 tests=[AWL=1.293, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] 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 GUEGV9cvY-tH for ; Wed, 6 May 2009 02:21:35 -0700 (PDT) Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id BD5FB3A6DBD for ; Wed, 6 May 2009 02:21:08 -0700 (PDT) Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ700INGU18C6@szxga01-in.huawei.com> for rrg@irtf.org; Wed, 06 May 2009 17:22:21 +0800 (CST) Received: from x41208a ([10.111.12.94]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KJ700KR0U18WV@szxga01-in.huawei.com> for rrg@irtf.org; Wed, 06 May 2009 17:22:20 +0800 (CST) Date: Wed, 06 May 2009 17:22:20 +0800 From: Xu Xiaohu In-reply-to: <4A0142DE.7040007@raszuk.net> To: robert@raszuk.net, 'Toni Stoev' Message-id: <001201c9ce2c$285546d0$5e0c6f0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcnOIKWjnO2zeMx3TdC5fRXg2sooQQACVs7g Cc: 'IRTF RRG' Subject: Re: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 09:21:42 -0000 > Just FYI I and Enke Chen have discussed in the past an > algorithmic way to convert 4 byte AS number into the locator. > Naturally such locator would be an anycast and one could most > likely enter given AS via any peering ASBR. In the draft of "Simple Tunnel Endpoint Signalling in BGP"[ http://tools.ietf.org/id/draft-xu-tunnel-00.txt ] , an IP address specific extended community is used for carring the tunnel endpoint (RLOC), which is associated with the NLRI (EID prefix). In fact, as long as the tunnel endpoint address is an anycast address within the originator AS , it is just AS-based inter-domain routing. Xiaohu > The scheme is very simple. > > We take 4 byte AS number, assume that we will use 3 last > octets while first octet would be all zeros and do normal > byte by byte bin to dec conversion. > > The resulting special IPv4 address would be 0.A.B.C. > > For IPv6 this is even simpler :). > > At that time some folks voiced their opinion that making AS > part of a locator is a bad thing. Along the same lines they > were against tunneling to AS/IP address. Perhaps those folks > could comment now why this is a bad choice ? > > I never understood why we can not make first baby step and > introduce some of the hierarchy just by doing this. We pretty > much already know today the originator AS from AS_PATH (AS > SET is sporadic) as well as number of potentially injected > new entires equal to number of ASes would be noise for current BGP. > > Cheers, > R. > > > How can locator have default association with its > containing autonomous system? > > Easy. Autonomous system number shall be incorporated into > locator. Universally recognizable locator shall start with it. > > > > On Tuesday 5 May 2009 12:35:41 Toni Stoev sent: > >> Intra-domain routing can be considered as a general > solution. This general solution is the provision of > reachability throughout an autonomous system. > >> Node locators can be considered intra-domain locators. > Every locator shall have default association with its > containing autonomous system in order to be universally recognizable. > >> Utilizing these approaches inter-domain routing can be > separated from intra-domain routing. Inter-domain routing > shall be based on autonomous system paths and not on IP > addresses and prefixes. Thus inter-domain routing tables will > be substantially unloaded and more easily managed. > >> This will provide significant improvement to inter-domain > routing scalability. > > _______________________________________________ > rrg mailing list > rrg@irtf.org > http://www.irtf.org/mailman/listinfo/rrg From irtf@tonistoev.info Wed May 6 19:38:47 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FA393A6F51 for ; Wed, 6 May 2009 19:38:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.04 X-Spam-Level: X-Spam-Status: No, score=-2.04 tagged_above=-999 required=5 tests=[AWL=0.559, 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 qBdMJL2cKtcx for ; Wed, 6 May 2009 19:38:46 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 891673A6F59 for ; Wed, 6 May 2009 19:38:46 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M1tWp-0003AU-M6 for rrg@irtf.org; Thu, 07 May 2009 05:40:07 +0300 From: Toni Stoev Date: Thu, 7 May 2009 05:40:05 +0300 User-Agent: KMail/1.9.9 References: <200905051235.41286.irtf@tonistoev.info> <200905060235.52415.irtf@tonistoev.info> In-Reply-To: <200905060235.52415.irtf@tonistoev.info> MIME-Version: 1.0 Content-Disposition: inline To: IRTF RRG Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200905070540.06216.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 02:38:47 -0000 Robert, Xiaohu, thanks for commenting. To be clear, I use the term "autonomous system" in the sense of "routing domain", considering both interchangeable. On Wednesday 6 May 2009 02:35:52 Toni Stoev sent: > How can locator have default association with its containing autonomous system? > Easy. Autonomous system number shall be incorporated into locator. Universally recognizable locator shall start with it. > > On Tuesday 5 May 2009 12:35:41 Toni Stoev sent: > > Intra-domain routing can be considered as a general solution. This general solution is the provision of reachability throughout an autonomous system. > > Node locators can be considered intra-domain locators. Every locator shall have default association with its containing autonomous system in order to be universally recognizable. > > Utilizing these approaches inter-domain routing can be separated from intra-domain routing. Inter-domain routing shall be based on autonomous system paths and not on IP addresses and prefixes. Thus inter-domain routing tables will be substantially unloaded and more easily managed. > > This will provide significant improvement to inter-domain routing scalability. > > _______________________________________________ > > rrg mailing list > > rrg@irtf.org > > http://www.irtf.org/mailman/listinfo/rrg > > > _______________________________________________ > rrg mailing list > rrg@irtf.org > http://www.irtf.org/mailman/listinfo/rrg > From HeinerHummel@aol.com Thu May 7 02:03:08 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1AE43A6F43 for ; Thu, 7 May 2009 02:03:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.911 X-Spam-Level: X-Spam-Status: No, score=-0.911 tagged_above=-999 required=5 tests=[AWL=1.087, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_43=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 gGSs50TRCuRo for ; Thu, 7 May 2009 02:03:03 -0700 (PDT) Received: from imr-d03.mx.aol.com (imr-d03.mx.aol.com [205.188.157.41]) by core3.amsl.com (Postfix) with ESMTP id 4C0863A68AD for ; Thu, 7 May 2009 02:03:03 -0700 (PDT) Received: from imo-da03.mx.aol.com (imo-da03.mx.aol.com [205.188.169.201]) by imr-d03.mx.aol.com (v107.10) with ESMTP id RELAYIN1-24a02a3e2ad; Thu, 07 May 2009 05:03:30 -0400 Received: from HeinerHummel@aol.com by imo-da03.mx.aol.com (mail_out_v40_r1.5.) id a.c47.57d61c3f (42805); Thu, 7 May 2009 05:03:26 -0400 (EDT) From: HeinerHummel@aol.com Message-ID: Date: Thu, 7 May 2009 05:03:26 EDT To: irtf@tonistoev.info, rrg@irtf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1241687006" X-Mailer: 9.0 SE for Windows sub 5021 X-AOL-IP: 205.188.169.201 Subject: Re: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 09:03:08 -0000 -------------------------------1241687006 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Toni, An important question is: what means "routable" ? Is an address routable= because it is "summarizable" ? Most IETF-folks think so, whereas I do not.= IMHO, neither a HIT, nor an IPv4/6 address nor an AS number is routable.= Well,wrt these, just IPv4/6 unicast addresses are summarizable. Your prop= osal tends towards E.164 (enum inverse :-), right ? Heiner In einer eMail vom 07.05.2009 04:40:32 Westeurop=E4ische Normalzeit schrei= bt irtf@tonistoev.info: Robert, Xiaohu, thanks for commenting. To be clear, I use the term "autonomous system" in the sense of "routing= domain", considering both interchangeable. On Wednesday 6 May 2009 02:35:52 Toni Stoev sent: > How can locator have default association with its containing autonomous= system? > Easy. Autonomous system number shall be incorporated into locator. Universally recognizable locator shall start with it. > > On Tuesday 5 May 2009 12:35:41 Toni Stoev sent: > > Intra-domain routing can be considered as a general solution. This = general solution is the provision of reachability throughout an autonomous= system. > > Node locators can be considered intra-domain locators. Every locator= shall have default association with its containing autonomous system in= order to be universally recognizable. > > Utilizing these approaches inter-domain routing can be separated from= intra-domain routing. Inter-domain routing shall be based on autonomous= system paths and not on IP addresses and prefixes. Thus inter-domain rout= ing tables will be substantially unloaded and more easily managed. > > This will provide significant improvement to inter-domain routing scalability. > > _______________________________________________ > > rrg mailing list > > rrg@irtf.org > > http://www.irtf.org/mailman/listinfo/rrg > > > _______________________________________________ > rrg mailing list > rrg@irtf.org > http://www.irtf.org/mailman/listinfo/rrg > _______________________________________________ rrg mailing list rrg@irtf.org http://www.irtf.org/mailman/listinfo/rrg -------------------------------1241687006 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
Toni,
An important question is: what means "routable" ? Is an address routa= ble because it is "summarizable" ? Most IETF-folks think so, whereas I do= not. IMHO, neither a HIT, nor an IPv4/6 address nor an AS number is routable.= Well,wrt these, just IPv4/6 unicast addresses are summarizable. Your= proposal tends towards  E.164 (enum inverse :-), right ?
 
Heiner
 
 
In einer eMail vom 07.05.2009 04:40:32 Westeurop=E4ische Normalzeit= schreibt irtf@tonistoev.info:
Robert, Xiaohu, thanks for commenting.

To be clear, I use the term "auton= omous system" in the sense of "routing domain", considering both interchangeable.

On Wednesday 6 May 2009 02:35:52 Toni Stoev sent:
> How can locator have default association with its containi= ng autonomous system?
> Easy. Autonomous system number shall be incorporated into locator. Universally recognizable locator shall start= with it.
>
> On Tuesday 5 May 2009 12:35:41 Toni Stoev sent:
= > > Intra-domain routing can be considered as a general solution. This= general solution is the provision of reachability throughout an autonomo= us system.
> > Node locators can be considered intra-domain locato= rs. Every locator shall have default association with its containing autonom= ous system in order to be universally recognizable.
> > Utilizing= these approaches inter-domain routing can be separated from intra-domain routi= ng. Inter-domain routing shall be based on autonomous system paths and not= on IP addresses and prefixes. Thus inter-domain routing tables will be substan= tially unloaded and more easily managed.
> > This will provide signifi= cant improvement to inter-domain routing scalability.
> > _______________________________________________
> > rrg mailing= list
> > rrg@irtf.org
> > http://www.irtf.org/mailman/listinfo/rrg
> >
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>
____________________= ___________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg
 
-------------------------------1241687006-- From scott.brim@gmail.com Thu May 7 04:41:56 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2AC683A6B07 for ; Thu, 7 May 2009 04:41:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=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 u9bbDGmO8zjb for ; Thu, 7 May 2009 04:41:55 -0700 (PDT) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by core3.amsl.com (Postfix) with ESMTP id E71A33A6BF0 for ; Thu, 7 May 2009 04:41:54 -0700 (PDT) Received: by qw-out-2122.google.com with SMTP id 3so512905qwe.7 for ; Thu, 07 May 2009 04:43:21 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=pKR0GfK8EpV0B7/wGKp+1DhLirsIe5LD15/IXiGRamE=; b=V7nmlTzrGQcx3cPrigZLdIGLXyqfv22Kiv2PYNSDdqhnEBt4QQzqsvtGHImqa2mmW2 d3Avo3JTphJSiSN28AfP3wRjThbz0hAN1bInyfNsR67P2UU7KvZzBjgaKtWQtg/QhTHH uF08oT4RyW2kA8l8uWyFBI1LrwnhYc6vF5Rqw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=nTm1fnwrfuGt4ghfaDTPeKc0/F4NEa51PVurmCClM71qaXjzkQqrlRG+ejqx0dgGAn N0ODnhzjx/KkrUDnMXbuO9B+LFu/0E3QuXQx3cjGaL4SZCO7yaIHXqqDtWd1B7dmy+Sj wboiFdoID1i+GHxb2ZxOpWcxL7gojwpFs0hf0= Received: by 10.224.74.82 with SMTP id t18mr2303763qaj.144.1241696601702; Thu, 07 May 2009 04:43:21 -0700 (PDT) Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id 7sm3579909qwb.18.2009.05.07.04.43.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 07 May 2009 04:43:21 -0700 (PDT) Message-ID: <4A02C956.50704@gmail.com> Date: Thu, 07 May 2009 07:43:18 -0400 From: Scott Brim User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: Toni Stoev References: <200905051235.41286.irtf@tonistoev.info> In-Reply-To: <200905051235.41286.irtf@tonistoev.info> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: IRTF RRG Subject: Re: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 11:41:56 -0000 Toni Stoev allegedly wrote on 05 05 2009 5:35 AM: > Intra-domain routing can be considered as a general solution. This > general solution is the provision of reachability throughout an > autonomous system. Node locators can be considered intra-domain > locators. Every locator shall have default association with its > containing autonomous system in order to be universally recognizable. First, see http://tools.ietf.org/html/rfc1955 Second, IMHO AS#s are the wrong granularity. - a prefix can be reachable via more than one AS - there can be more than one prefix within an AS - it should be possible to route different prefixes, and subprefixes, via different paths for traffic engineering purposes. Scott From scott.brim@gmail.com Thu May 7 04:46:52 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD0E63A6BF0 for ; Thu, 7 May 2009 04:46:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_43=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 nEYFK1Bkscrc for ; Thu, 7 May 2009 04:46:52 -0700 (PDT) Received: from mail-qy0-f123.google.com (mail-qy0-f123.google.com [209.85.221.123]) by core3.amsl.com (Postfix) with ESMTP id 559753A6EBD for ; Thu, 7 May 2009 04:46:37 -0700 (PDT) Received: by qyk29 with SMTP id 29so1233509qyk.15 for ; Thu, 07 May 2009 04:48:03 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=NRIyYwK8tOnKplZOLQ3zv2jnQXNmdxPxbpEw1nSi8MQ=; b=lyZL+z5+VbNJbc2Tx3C4XGIcyY/IALAJpSSBkAjZK9jGf1OVVWJjtfb1vp4jMemZT0 PVsqe1yqIk11aldx0JOykKZMsBIHiAKB6v3dmwP/0DXHzG856amqmZanssynWnYX2v7n vMUOvh9lh753mVH7YoH90Nov3W7Eg/nbbhBDs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=ld0Ipy6NnOpd6hlNSTY8X2HHt3S6zWNr5Um/hXIBfT0xOO6Cmcfu69unpxLsIjOdYT rsRABKzEpbK1Kx5VPc6rdDG85EGOtx+QcS7Z52Y93juHr1ffMcxawtwDRgJlbO5kKCJ4 aljEt4w9UrqUgZbXrQTKqtos+rDlW0P02NfS4= Received: by 10.224.73.210 with SMTP id r18mr2292236qaj.264.1241696883210; Thu, 07 May 2009 04:48:03 -0700 (PDT) Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id 7sm3633361qwf.45.2009.05.07.04.48.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 07 May 2009 04:48:02 -0700 (PDT) Message-ID: <4A02CA71.5050106@gmail.com> Date: Thu, 07 May 2009 07:48:01 -0400 From: Scott Brim User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: HeinerHummel@aol.com References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: rrg@irtf.org Subject: Re: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 11:46:52 -0000 HeinerHummel@aol.com allegedly wrote on 05 07 2009 5:03 AM: > > Toni, > An important question is: what means "routable" ? Is an address routable > because it is "summarizable" ? Most IETF-folks think so, whereas I do > not. IMHO, neither a HIT, nor an IPv4/6 address nor an AS number is > routable. Well,wrt these, just IPv4/6 unicast addresses are > summarizable. Your proposal tends towards E.164 (enum inverse :-), right ? Anything that names a point of attachment to the network is "routable". "Routable" just means that information about its topological location can be propagated and used by forwarding. The reason we say that location naming has to follow topology is for aggregation. From jnc@mercury.lcs.mit.edu Thu May 7 04:47:25 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5EB8E3A6BF0 for ; Thu, 7 May 2009 04:47:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.49 X-Spam-Level: X-Spam-Status: No, score=-6.49 tagged_above=-999 required=5 tests=[AWL=0.109, 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 KVxb0Xukq+LB for ; Thu, 7 May 2009 04:47:24 -0700 (PDT) Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 947C53A6A09 for ; Thu, 7 May 2009 04:47:24 -0700 (PDT) Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 9A3126BE601; Thu, 7 May 2009 07:48:51 -0400 (EDT) To: rrg@irtf.org Message-Id: <20090507114851.9A3126BE601@mercury.lcs.mit.edu> Date: Thu, 7 May 2009 07:48:51 -0400 (EDT) From: jnc@mercury.lcs.mit.edu (Noel Chiappa) Cc: jnc@mercury.lcs.mit.edu Subject: Re: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 11:47:25 -0000 > From: Scott Brim > it should be possible to route different prefixes, and subprefixes, > via different paths for traffic engineering purposes. You guys are discussing whether buggy whips should have brass handles or not. This is the Routing RESEARCH Group, for goodness' sake! Noel From HeinerHummel@aol.com Thu May 7 05:00:30 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 144FE3A6EC3 for ; Thu, 7 May 2009 05:00:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.994 X-Spam-Level: X-Spam-Status: No, score=-0.994 tagged_above=-999 required=5 tests=[AWL=1.004, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_43=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 Sw43lMy0tDXW for ; Thu, 7 May 2009 05:00:29 -0700 (PDT) Received: from imr-d06.mx.aol.com (imr-d06.mx.aol.com [205.188.159.7]) by core3.amsl.com (Postfix) with ESMTP id 2F6F83A6E11 for ; Thu, 7 May 2009 05:00:29 -0700 (PDT) Received: from imo-da02.mx.aol.com (imo-da02.mx.aol.com [205.188.169.200]) by imr-d06.mx.aol.com (v107.10) with ESMTP id RELAYIN3-44a02cda1317; Thu, 07 May 2009 08:01:37 -0400 Received: from HeinerHummel@aol.com by imo-da02.mx.aol.com (mail_out_v40_r1.5.) id o.c52.4de9031d (48552); Thu, 7 May 2009 08:01:33 -0400 (EDT) From: HeinerHummel@aol.com Message-ID: Date: Thu, 7 May 2009 08:02:44 EDT To: scott.brim@gmail.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1241697764" X-Mailer: 9.0 SE for Windows sub 5021 X-AOL-IP: 205.188.169.200 Cc: rrg@irtf.org Subject: Re: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 12:00:30 -0000 -------------------------------1241697764 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable In einer eMail vom 07.05.2009 13:48:12 Westeurop=E4ische Normalzeit schrei= bt scott.brim@gmail.com: HeinerHummel@aol.com allegedly wrote on 05 07 2009 5:03 AM: > > Toni, > An important question is: what means "routable" ? Is an address routabl= e > because it is "summarizable" ? Most IETF-folks think so, whereas I do > not. IMHO, neither a HIT, nor an IPv4/6 address nor an AS number is > routable. Well,wrt these, just IPv4/6 unicast addresses are > summarizable. Your proposal tends towards E.164 (enum inverse :-), right ? Anything that names a point of attachment to the network is "routable". "Routable" just means that information about its topological location can be propagated and used by forwarding. The reason we say that location naming has to follow topology is for aggregation. Yes, but for a very high price: update churn, table size, Moore's law made= unapplicable. Heiner -------------------------------1241697764 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
In einer eMail vom 07.05.2009 13:48:12 Westeurop=E4ische Normalzeit= schreibt scott.brim@gmail.com:
HeinerHummel@aol.com allegedly wrote on 05 07 2009 5:03 AM:
= >
> Toni,
> An important question is: what means "routable"= ? Is an address routable
> because it is "summarizable" ? Most IETF-folks= think so, whereas I do
> not. IMHO, neither a HIT, nor an IPv4/6 address= nor an AS number is
> routable. Well,wrt these, just IPv4/6 unicast addresses are
> summarizable. Your proposal tends towards  E.= 164 (enum inverse :-), right ?

Anything that names a point of attachm= ent to the network is "routable".
   "Routable" just means that information about its topological location
can be propagated and used= by forwarding.  The reason we say that
location naming has to follo= w topology is for aggregation.
Yes, but for a very high price: update churn, table size, Moore's law= made unapplicable.
 
Heiner
-------------------------------1241697764-- From louise.burness@bt.com Thu May 7 08:23:25 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F11003A6898 for ; Thu, 7 May 2009 08:23:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.26 X-Spam-Level: X-Spam-Status: No, score=-1.26 tagged_above=-999 required=5 tests=[AWL=1.739, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_LOW=-1] 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 tDFqhKsRsBfO for ; Thu, 7 May 2009 08:23:25 -0700 (PDT) Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151]) by core3.amsl.com (Postfix) with ESMTP id EA5D33A683D for ; Thu, 7 May 2009 08:23:24 -0700 (PDT) Received: from E03MVB2-UKBR.domain1.systemhost.net ([193.113.197.108]) by smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 7 May 2009 16:24:51 +0100 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: Thu, 7 May 2009 16:24:31 +0100 Message-ID: In-Reply-To: <4A02C956.50704@gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [rrg] Inter/intra-domain routing separation Thread-Index: AcnPCQtmUw+Ug/NxRc+BN5snI8PbCwAHTOBw From: To: , X-OriginalArrivalTime: 07 May 2009 15:24:51.0847 (UTC) FILETIME=[F76BA170:01C9CF27] Cc: rrg@irtf.org Subject: Re: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 15:23:26 -0000 =20 > -----Original Message----- > From: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] On=20 > Behalf Of Scott Brim > Sent: 07 May 2009 12:43 > To: Toni Stoev > Cc: IRTF RRG > Subject: Re: [rrg] Inter/intra-domain routing separation >=20 > Toni Stoev allegedly wrote on 05 05 2009 5:35 AM: > > Intra-domain routing can be considered as a general solution. This=20 > > general solution is the provision of reachability throughout an=20 > > autonomous system. Node locators can be considered intra-domain=20 > > locators. Every locator shall have default association with its=20 > > containing autonomous system in order to be universally=20 > recognizable. >=20 > First, see http://tools.ietf.org/html/rfc1955 >=20 > Second, IMHO AS#s are the wrong granularity. >=20 > - a prefix can be reachable via more than one AS >=20 > - there can be more than one prefix within an AS >=20 > - it should be possible to route different prefixes, and=20 > subprefixes, > via different paths for traffic engineering purposes. Why should we do that at the level of prefix - would it not be nicer to route different traffic via different paths to load balance based on load - who really wants to prefix balance.=20 Also, a computer can be reached by more than one prefix as well as more than one AS If we assume we have an end point identifier then would AS be the wrong level of granularity for the top level of a routing heirarchy? Seems to me that the prefix level is too detailed for us to handle well so we need to make the top level less fine grained?=20 Louise >=20 > Scott > _______________________________________________ > rrg mailing list > rrg@irtf.org > http://www.irtf.org/mailman/listinfo/rrg >=20 From irtf@tonistoev.info Thu May 7 15:44:25 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE0EC3A6C3B for ; Thu, 7 May 2009 15:44:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.075 X-Spam-Level: X-Spam-Status: No, score=-2.075 tagged_above=-999 required=5 tests=[AWL=0.524, 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 EZzvrW5u-Y4y for ; Thu, 7 May 2009 15:44:25 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id EF3883A68B6 for ; Thu, 7 May 2009 15:44:24 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M2CLd-0001bg-1W for rrg@irtf.org; Fri, 08 May 2009 01:45:49 +0300 From: Toni Stoev To: IRTF RRG Date: Fri, 8 May 2009 01:45:48 +0300 User-Agent: KMail/1.9.9 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905080145.48786.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: [rrg] Default intra-domain routing X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 22:44:25 -0000 Researchers, Do we want a single default intra-domain routing mechanism providing reachability throughout a routing domain? From irtf@tonistoev.info Thu May 7 16:14:01 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C6863A6DA1 for ; Thu, 7 May 2009 16:14:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.106 X-Spam-Level: X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[AWL=0.493, 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 wTlrm0UpTjpj for ; Thu, 7 May 2009 16:14:01 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id C82FC3A6C5E for ; Thu, 7 May 2009 16:14:00 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M2CoH-0007Y6-B0 for rrg@irtf.org; Fri, 08 May 2009 02:15:25 +0300 From: Toni Stoev Date: Fri, 8 May 2009 02:15:23 +0300 User-Agent: KMail/1.9.9 References: <200905080145.48786.irtf@tonistoev.info> In-Reply-To: <200905080145.48786.irtf@tonistoev.info> MIME-Version: 1.0 Content-Disposition: inline To: IRTF RRG Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200905080215.24142.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [rrg] Default intra-domain routing X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 23:14:01 -0000 Do we want the default intra-domain routing mechanism to be based on locators? > Do we want a single default intra-domain routing mechanism providing reachability throughout a routing domain? From irtf@tonistoev.info Thu May 7 16:51:27 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6FB2D3A6E32 for ; Thu, 7 May 2009 16:51:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.133 X-Spam-Level: X-Spam-Status: No, score=-2.133 tagged_above=-999 required=5 tests=[AWL=0.466, 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 A4RQ2TpgBp4e for ; Thu, 7 May 2009 16:51:26 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id D37E93A69D7 for ; Thu, 7 May 2009 16:51:21 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M2DOQ-00065y-5e for rrg@irtf.org; Fri, 08 May 2009 02:52:46 +0300 From: Toni Stoev Date: Fri, 8 May 2009 02:52:45 +0300 User-Agent: KMail/1.9.9 References: <200905080145.48786.irtf@tonistoev.info> <200905080215.24142.irtf@tonistoev.info> In-Reply-To: <200905080215.24142.irtf@tonistoev.info> MIME-Version: 1.0 Content-Disposition: inline To: IRTF RRG Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200905080252.45861.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [rrg] Default intra-domain routing X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 23:51:27 -0000 How about default intra-domain routing mechanism utilizing just locator longest match? > Do we want the default intra-domain routing mechanism to be based on locators? > > Do we want a single default intra-domain routing mechanism providing reachability throughout a routing domain? From irtf@tonistoev.info Thu May 7 18:06:40 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 45D663A6A75 for ; Thu, 7 May 2009 18:06:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.158 X-Spam-Level: X-Spam-Status: No, score=-2.158 tagged_above=-999 required=5 tests=[AWL=0.441, 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 KRhnKFPHJRBW for ; Thu, 7 May 2009 18:06:39 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 5F3953A6EB9 for ; Thu, 7 May 2009 18:06:23 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M2EZ1-0003Km-DF for rrg@irtf.org; Fri, 08 May 2009 04:07:47 +0300 From: Toni Stoev To: IRTF RRG Date: Fri, 8 May 2009 04:07:47 +0300 User-Agent: KMail/1.9.9 References: <200905080145.48786.irtf@tonistoev.info> <200905080215.24142.irtf@tonistoev.info> <200905080252.45861.irtf@tonistoev.info> In-Reply-To: <200905080252.45861.irtf@tonistoev.info> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905080407.47253.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [rrg] Default intra-domain routing X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 May 2009 01:06:40 -0000 And how about objective and accurate native determination of routing domain based on locators? > How about default intra-domain routing mechanism utilizing just locator longest match? > > Do we want the default intra-domain routing mechanism to be based on locators? > > > Do we want a single default intra-domain routing mechanism providing reachability throughout a routing domain? From irtf@tonistoev.info Thu May 7 18:53:01 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69EB83A6C6D for ; Thu, 7 May 2009 18:53:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.18 X-Spam-Level: X-Spam-Status: No, score=-2.18 tagged_above=-999 required=5 tests=[AWL=0.419, 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 YFZj89hHJwXO for ; Thu, 7 May 2009 18:53:00 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 8AD3B3A6C02 for ; Thu, 7 May 2009 18:53:00 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M2FI8-0000T3-5W for rrg@irtf.org; Fri, 08 May 2009 04:54:24 +0300 From: Toni Stoev To: IRTF RRG Date: Fri, 8 May 2009 04:54:23 +0300 User-Agent: KMail/1.9.9 References: <200905080145.48786.irtf@tonistoev.info> <200905080252.45861.irtf@tonistoev.info> <200905080407.47253.irtf@tonistoev.info> In-Reply-To: <200905080407.47253.irtf@tonistoev.info> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905080454.24038.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [rrg] Default intra-domain routing X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 May 2009 01:53:01 -0000 Now, to the point of scalability: Does locator have to fit into IPv6 address field or can it have its own appropriate appearance? > And how about objective and accurate native determination of routing domain based on locators? > > How about default intra-domain routing mechanism utilizing just locator longest match? > > > Do we want the default intra-domain routing mechanism to be based on locators? > > > > Do we want a single default intra-domain routing mechanism providing reachability throughout a routing domain? IRTF Research Group Guidelines and Procedures: ... The IRTF focuses on longer term research issues related to the Internet... From xuxh@huawei.com Thu May 7 20:26:39 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 59BC73A69E8 for ; Thu, 7 May 2009 20:26:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.422 X-Spam-Level: ** X-Spam-Status: No, score=2.422 tagged_above=-999 required=5 tests=[AWL=-0.472, BAYES_00=-2.599, CN_BODY_35=0.339, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_21=0.6, MIME_CHARSET_FARAWAY=2.45, RDNS_NONE=0.1] 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 3oa4CkQCRXaX for ; Thu, 7 May 2009 20:26:38 -0700 (PDT) Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id E46313A6A1A for ; Thu, 7 May 2009 20:25:42 -0700 (PDT) Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJB008L42R0S6@szxga04-in.huawei.com> for rrg@irtf.org; Fri, 08 May 2009 11:23:24 +0800 (CST) Received: from x41208a ([10.111.12.94]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KJB0020V2QZW9@szxga04-in.huawei.com> for rrg@irtf.org; Fri, 08 May 2009 11:23:24 +0800 (CST) Date: Fri, 08 May 2009 11:23:23 +0800 From: Xu Xiaohu In-reply-to: <4A02C956.50704@gmail.com> To: 'Scott Brim' , 'Toni Stoev' Message-id: <001701c9cf8c$585de790$5e0c6f0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=gb2312 Content-transfer-encoding: quoted-printable Thread-index: AcnPCR8WWchnEupfTB2KrMbnEVlsKAAgdOtQ Cc: 'IRTF RRG' Subject: Re: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 May 2009 03:26:39 -0000 > -----=D3=CA=BC=FE=D4=AD=BC=FE----- > =B7=A2=BC=FE=C8=CB: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] = =B4=FA=B1=ED Scott Brim > =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA5=D4=C27=C8=D5 19:43 > =CA=D5=BC=FE=C8=CB: Toni Stoev > =B3=AD=CB=CD: IRTF RRG > =D6=F7=CC=E2: Re: [rrg] Inter/intra-domain routing separation >=20 > Toni Stoev allegedly wrote on 05 05 2009 5:35 AM: > > Intra-domain routing can be considered as a general solution. This=20 > > general solution is the provision of reachability throughout an=20 > > autonomous system. Node locators can be considered intra-domain=20 > > locators. Every locator shall have default association with its=20 > > containing autonomous system in order to be universally=20 > recognizable. >=20 > First, see http://tools.ietf.org/html/rfc1955 >=20 > Second, IMHO AS#s are the wrong granularity. How about providing enough flexibility so that both AS granularity and prefix granularity are available? For example, those tunnel endpoint routers (ETR) within the same AS could either use unique unicast = addresses per router or an anycast address as their tunnel endpoint addresses = (RLOC). Xiaohu > - a prefix can be reachable via more than one AS >=20 > - there can be more than one prefix within an AS >=20 > - it should be possible to route different prefixes, and=20 > subprefixes, > via different paths for traffic engineering purposes. >=20 > Scott > _______________________________________________ > rrg mailing list > rrg@irtf.org > http://www.irtf.org/mailman/listinfo/rrg From irtf@tonistoev.info Fri May 8 03:17:52 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A1653A6ABF for ; Fri, 8 May 2009 03:17:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.2 X-Spam-Level: X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=0.399, 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 PQMs0IFwDYPq for ; Fri, 8 May 2009 03:17:51 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 893383A684F for ; Fri, 8 May 2009 03:17:51 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M2NAi-0006Ws-0U for rrg@irtf.org; Fri, 08 May 2009 13:19:16 +0300 From: Toni Stoev To: IRTF RRG Date: Fri, 8 May 2009 13:19:15 +0300 User-Agent: KMail/1.9.9 References: <4A02CA71.5050106@gmail.com> In-Reply-To: <4A02CA71.5050106@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905081319.15142.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 May 2009 10:17:52 -0000 Scott Brim wrote: > The reason we say that > location naming has to follow topology is for aggregation. In my not humble opinion, location naming has to follow reachability. So having location we know how to reach. From irtf@tonistoev.info Fri May 8 03:51:48 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BDDAC3A6C78 for ; Fri, 8 May 2009 03:51:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.218 X-Spam-Level: X-Spam-Status: No, score=-2.218 tagged_above=-999 required=5 tests=[AWL=0.381, 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 Q-wyGRHgL-wO for ; Fri, 8 May 2009 03:51:48 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id EBB883A6B1F for ; Fri, 8 May 2009 03:51:47 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M2NhZ-0005KU-5U for rrg@irtf.org; Fri, 08 May 2009 13:53:13 +0300 From: Toni Stoev Date: Fri, 8 May 2009 13:53:12 +0300 User-Agent: KMail/1.9.9 References: <200904301413.20693.irtf@tonistoev.info> In-Reply-To: <200904301413.20693.irtf@tonistoev.info> MIME-Version: 1.0 Content-Disposition: inline To: IRTF RRG Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200905081353.12210.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [rrg] More terminology X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 May 2009 10:51:48 -0000 Some more terminology: Term: neighbor Definition: node in relation to another node, at the presence of a link between the two > I propose basic definitions of a few terms: > > Term: network > Definition: aggregate of interlinked objects > > Term: node > Definition: object engaged in a network > > Term: link > Definition: medium of communication between nodes > _______________________________________________ > rrg mailing list > rrg@irtf.org > http://www.irtf.org/mailman/listinfo/rrg > From HeinerHummel@aol.com Fri May 8 07:07:42 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E46173A6CC0 for ; Fri, 8 May 2009 07:07:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.093 X-Spam-Level: X-Spam-Status: No, score=0.093 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_50=0.001, HTML_MESSAGE=0.001] 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 a4jga52UyPiI for ; Fri, 8 May 2009 07:07:42 -0700 (PDT) Received: from imr-d03.mx.aol.com (imr-d03.mx.aol.com [205.188.157.41]) by core3.amsl.com (Postfix) with ESMTP id 207583A6B78 for ; Fri, 8 May 2009 07:07:41 -0700 (PDT) Received: from imo-ma02.mx.aol.com (imo-ma02.mx.aol.com [64.12.78.137]) by imr-d03.mx.aol.com (v107.10) with ESMTP id RELAYIN2-34a043ccf18c; Fri, 08 May 2009 10:08:15 -0400 Received: from HeinerHummel@aol.com by imo-ma02.mx.aol.com (mail_out_v40_r1.5.) id a.d0f.497a28e8 (41812); Fri, 8 May 2009 10:07:51 -0400 (EDT) From: HeinerHummel@aol.com Message-ID: Date: Fri, 8 May 2009 10:07:50 EDT To: irtf@tonistoev.info, rrg@irtf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1241791670" X-Mailer: 9.0 SE for Windows sub 5021 X-AOL-IP: 64.12.78.137 Subject: Re: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 May 2009 14:07:43 -0000 -------------------------------1241791670 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable In einer eMail vom 08.05.2009 12:19:32 Westeurop=E4ische Normalzeit schrei= bt irtf@tonistoev.info: In my not humble opinion, location naming has to follow reachability. So having location we know how to reach. In my humble opinion, location naming should follow routability. Heiner -------------------------------1241791670 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
In einer eMail vom 08.05.2009 12:19:32 Westeurop=E4ische Normalzeit= schreibt irtf@tonistoev.info:
In my not humble opinion, location naming has to follow reachability.
So ha= ving location we know how to reach.
In my humble opinion, location naming should follow routability.=
Heiner
-------------------------------1241791670-- From vijay@gatech.edu Mon May 11 09:32:52 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1844C28C15E for ; Mon, 11 May 2009 09:32:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.076 X-Spam-Level: X-Spam-Status: No, score=-1.076 tagged_above=-999 required=5 tests=[AWL=-1.077, BAYES_50=0.001] 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 A2lHpXrvAbA0 for ; Mon, 11 May 2009 09:32:52 -0700 (PDT) Received: from deliverator5.ecc.gatech.edu (deliverator5.ecc.gatech.edu [130.207.185.175]) by core3.amsl.com (Postfix) with ESMTP id DBEC63A6A26 for ; Mon, 11 May 2009 09:32:28 -0700 (PDT) Received: from deliverator5.ecc.gatech.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id EFD511801B8 for ; Mon, 11 May 2009 12:33:58 -0400 (EDT) Received: from mail6.gatech.edu (bigip.ecc.gatech.edu [130.207.185.140]) by deliverator5.ecc.gatech.edu (Postfix) with ESMTP id 808C71801BB for ; Mon, 11 May 2009 12:33:58 -0400 (EDT) Received: from mail6.gatech.edu (localhost [127.0.0.1]) by mail6.gatech.edu (Postfix) with ESMTP id 3F323225AA2 for ; Mon, 11 May 2009 12:33:58 -0400 (EDT) Date: Mon, 11 May 2009 12:33:58 -0400 (EDT) From: "Balasubramaniyan, Vijay A" To: rrg@irtf.org Message-ID: <1605038663.7746271242059638227.JavaMail.root@mail6.gatech.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [130.207.185.161] X-Mailer: Zimbra 5.0.15_GA_2851.RHEL5_64 (ZimbraWebClient - FF3.0 (Linux)/5.0.15_GA_2851.RHEL5_64) Subject: [rrg] CFP NPSec 2009 Extended Deadline X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 May 2009 16:32:52 -0000 Dear colleagues, The deadlines for NPSec 2009 have been extended. The new deadlines are: Abstract submission: June 8, 2009 Paper submission: June 15, 2009 Thanks, Vijay Balasubramaniyan NPSec 2009 web and publicity chair [Apologies if you receive multiple copies of this CFP] CALL FOR PAPERS NPSec 2009 5th Workshop on Secure Network Protocols In conjunction with ICNP 2009 October 13, 2009 Princeton, New Jersey, USA http://www.gtisc.gatech.edu/npsec09/ Scope: The 5th workshop on Secure Network Protocols (NPSec) is a one-day event held in conjunction with the 17th IEEE International Conference on Network Protocols (ICNP 2009). NPSec focuses on two general areas. The first focus is on the development and analysis of secure or hardened protocols for the operation (establishment and maintenance) of network infrastructure, including such targets as secure multidomain, ad hoc, sensor or overlay networks, or other related target areas. This can include new protocols, enhancements to existing protocols, protocol analysis, and new attacks on existing protocols. The second focus is on employing such secure network protocols to create or enhance network applications. Examples include collaborative firewalls, incentive strategies for multiparty networks, and deployment strategies to enable secure applications. NPSec 2009 particularly welcomes new ideas on security in the context of future Internet design, such as architectural considerations for future Internet security and new primitives for supporting secure network protocol and application design. Topics of interest include but are not limited to: 1. security in future Internet architectures - role of security in future architectures - integrating security into future protocols and applications 2. secure and/or resilient network protocols, e.g.: - internetworking/routing - MANETs - LANs and WLANs - mobile/cellular data networks - p2p and other overlay networks - federated trust systems - sensor networks 3. vulnerabilities of existing protocols and applications (both theoretical and case studies), including attacks 4. key distribution/management 5. intrusion detection and response 6. incentive systems for p2p systems and MANETs routing 7. secure protocol configuration and deployment Important Dates: Abstract submission: June 8, 2009 Paper submission: June 15, 2009 Notification of acceptance: July 15, 2009 Camera ready version: August 5, 2009 NPSEC Steering Committee: Sonia Fahmy, Purdue University (chair) George Kesidis, Penn State University Cristina Nita-Rotaru, Purdue University Gene Tsudik, UC Irvine Program Co-Chairs: Jelena Mirkovic, USC/ISI Xiaowei Yang, Duke University Web and Proceedings Chair: Vijay A. Balasubramaniyan, Georgia Tech. Technical Program Committee: Daniel Massey, Colorado State University Jun Li, University of Oregon Peter Reiher, UCLA Beichuan Zhang, University of Arizona Young Cho, USC/ISI Mukesh Singhal, University of Kentucky Minseok Kwon, Rochester Institute of Technology Lan Wang, University of Memphis Y. Charlie Hu, Purdue University Minaxi Gupta, Indiana University Dan Pei, AT\&T Research Bogdan Carbunar, Motorola Research Ted Faber, USC/ISI Jia Wang, AT\&T Research Landon Cox, Duke University Jean-Pierre Hubaux, EPFL Stephan Bohacek, University of Delaware Reza Curtmola, New Jersey Institute of Technology Brent Kang, University of North Carolina Bryan Ford, Max Planck Institute for Software Systems From eric.fleischman@boeing.com Tue May 12 08:47:32 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED3073A6BAD for ; Tue, 12 May 2009 08:47:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.11 X-Spam-Level: X-Spam-Status: No, score=-5.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 39Ti-PWd0uyU for ; Tue, 12 May 2009 08:47:32 -0700 (PDT) Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 34D173A6912 for ; Tue, 12 May 2009 08:47:32 -0700 (PDT) Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n4CFn32A026297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 12 May 2009 08:49:03 -0700 (PDT) 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 n4CFn2wU006047 for ; Tue, 12 May 2009 10:49:02 -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 n4CFmvNo005516 for ; Tue, 12 May 2009 10:49:02 -0500 (CDT) Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 12 May 2009 08:48:59 -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, 12 May 2009 08:48:58 -0700 Message-ID: <474EEBD229DF754FB83D256004D021080BB9A6F4@XCH-NW-6V1.nw.nos.boeing.com> In-Reply-To: <200905070540.06216.irtf@tonistoev.info> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [rrg] Inter/intra-domain routing separation Thread-Index: AcnOvSnJ6DURObQHQ9K7BgZuYU76FAEWfsXQ References: <200905051235.41286.irtf@tonistoev.info><200905060235.52415.irtf@tonistoev.info> <200905070540.06216.irtf@tonistoev.info> From: "Fleischman, Eric" To: "IRTF RRG" X-OriginalArrivalTime: 12 May 2009 15:48:59.0530 (UTC) FILETIME=[2A5F46A0:01C9D319] Subject: Re: [rrg] Inter/intra-domain routing separation X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 May 2009 15:47:33 -0000 It is my personal opinion that most of these definitions are already well established in Internet parlance and therefore re-definitions are not warranted (or needed). It is also my personal opinion that some of the recent postings could have been resolved by reference to well-established traditional architectural principals such as the IP Topology Hierarchy, which defines topology layers such as "autonomous systems" as well as routing concepts such as intra-domain and inter-domain. Coworkers who think as I do in terms of historic Internet constructs such as those articulated by Catenet, the ROAD Group, or NIMROD will probably think in terms of recursion and the possibility of creating complex structures within IP Topology Hierarchy layers. The power and beauty of this historic model when applied to the IP Topology Hierarchy framework is amazingly impressive. But that is the topic for another posting... The goal of this posting is solely to express my personal opinion that historic Internet concepts and traditional Internet terminology retain great value, power, and usefulness and should not easily be overlooked (or modified). From irtf@tonistoev.info Tue May 12 16:30:32 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC5FF3A6F99 for ; Tue, 12 May 2009 16:30:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.934 X-Spam-Level: X-Spam-Status: No, score=-0.934 tagged_above=-999 required=5 tests=[AWL=-0.935, BAYES_50=0.001] 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 XJ6shAc0hZcO for ; Tue, 12 May 2009 16:30:32 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 0A39B3A6FA5 for ; Tue, 12 May 2009 16:30:30 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M41S2-0002qx-6K for rrg@irtf.org; Wed, 13 May 2009 02:31:58 +0300 From: Toni Stoev Date: Wed, 13 May 2009 02:31:57 +0300 User-Agent: KMail/1.9.9 MIME-Version: 1.0 Content-Disposition: inline To: IRTF RRG Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200905130231.57818.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: [rrg] Locator X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 May 2009 23:30:32 -0000 Dear fellow researchers, I guess Tony has been abducted by real world beings. So I am continuing his brave efforts. Let us prepare locator for routing scalability. As an initial step, please share your opinion on the following question: In the general network, what does a universally recognizable locator actually name: a node, an interface, or something else? My opinion is that the locator must name a node. Toni From fred@cisco.com Tue May 12 16:55:09 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B788E28C188 for ; Tue, 12 May 2009 16:55:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.479 X-Spam-Level: X-Spam-Status: No, score=-106.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] 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 sy7-8rdA9UWh for ; Tue, 12 May 2009 16:55:08 -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 E18BE28C150 for ; Tue, 12 May 2009 16:55:08 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,184,1241395200"; d="scan'208";a="303336770" Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 12 May 2009 23:56:41 +0000 Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n4CNueWx017279; Tue, 12 May 2009 16:56:40 -0700 Received: from stealth-10-32-244-221.cisco.com (stealth-10-32-244-221.cisco.com [10.32.244.221]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n4CNueMW003473; Tue, 12 May 2009 23:56:40 GMT Message-Id: <36BE2317-796A-4D99-88E3-80DB673720CA@cisco.com> From: Fred Baker To: Toni Stoev In-Reply-To: <200905130231.57818.irtf@tonistoev.info> 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: Tue, 12 May 2009 16:56:40 -0700 References: <200905130231.57818.irtf@tonistoev.info> X-Mailer: Apple Mail (2.935.3) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=448; t=1242172601; x=1243036601; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20 |Subject:=20Re=3A=20[rrg]=20Locator |Sender:=20; bh=XTDBRjkwLoMENO4btQ+V/TBXOYWfvB+2tjNoRp2Qicc=; b=m31tJsZSkkMMIMtpIB1n3PioluApoOcRoDr5B7rzvwdazL6O2kHV3l93hi aOUPJrO2qYPe59tM4Q61591bnJNkz8Gep635Rfl60SK4AJpk7dvjGfA1R04B 3MvIiRAnVn; Authentication-Results: sj-dkim-3; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); Cc: IRTF RRG Subject: Re: [rrg] Locator X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 May 2009 23:55:09 -0000 On May 12, 2009, at 4:31 PM, Toni Stoev wrote: > In the general network, what does a universally recognizable locator > actually name: a node, an interface, or something else? That depends largely on your definition of a locator. RFC 1498 would have it name a node. RFC 1992 would have it name a transport connection endpoint - the underbelly of an application. LISP would have it name a network. GSE would have it name a LAN. From jnc@mercury.lcs.mit.edu Tue May 12 17:12:13 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C98AF3A67CF for ; Tue, 12 May 2009 17:12:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.492 X-Spam-Level: X-Spam-Status: No, score=-6.492 tagged_above=-999 required=5 tests=[AWL=0.107, 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 wsnG2CNAu922 for ; Tue, 12 May 2009 17:12:13 -0700 (PDT) Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 1413C3A6953 for ; Tue, 12 May 2009 17:12:12 -0700 (PDT) Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 9A8C96BE603; Tue, 12 May 2009 20:13:43 -0400 (EDT) To: rrg@irtf.org Message-Id: <20090513001343.9A8C96BE603@mercury.lcs.mit.edu> Date: Tue, 12 May 2009 20:13:43 -0400 (EDT) From: jnc@mercury.lcs.mit.edu (Noel Chiappa) Cc: jnc@mercury.lcs.mit.edu Subject: Re: [rrg] Locator X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2009 00:12:13 -0000 > From: Fred Baker > RFC 1992 would have it name a transport connection endpoint - the > underbelly of an application. Ah, no. To quote RFC-1992: "A locator ... identifies a location in an internetwork. Nodes and endpoint are assigned locators. Different nodes have necessarily different locators. A node is assigned only one locator. Locators identify nodes and specify *where* a node is in the network. Locators do *not* specify a path to the node." One also needs to be aware that in this document, "node" means 'network region', not 'host/router', as it is commonly taken to mean in networking: "A node represents a region of the physical network. The region of the network represented by a node can be as large or as small as desired: a node can represent a continent or a process running inside a host. Moreover .. a region of the network can simultaneously be represented by more than one node." (In the next section of the document, "node" is very precisely defined to mean 'map element' - from the node/arc terminology of graph theory, since maps are graphs - the above is just a 'starter definition'.) Noel From HeinerHummel@aol.com Wed May 13 00:49:09 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 959E728C1CE for ; Wed, 13 May 2009 00:49:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.621 X-Spam-Level: X-Spam-Status: No, score=-0.621 tagged_above=-999 required=5 tests=[AWL=0.488, BAYES_05=-1.11, HTML_MESSAGE=0.001] 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 irN-AOH-zDOO for ; Wed, 13 May 2009 00:49:08 -0700 (PDT) Received: from imo-m12.mail.aol.com (imo-m12.mx.aol.com [64.12.143.100]) by core3.amsl.com (Postfix) with ESMTP id 896ED3A6F38 for ; Wed, 13 May 2009 00:49:08 -0700 (PDT) Received: from imo-da04.mx.aol.com (imo-da04.mx.aol.com [205.188.169.202]) by imo-m12.mail.aol.com (v107.10) with ESMTP id RELAYIN2-34a0a7bc21af; Wed, 13 May 2009 03:50:26 -0400 Received: from HeinerHummel@aol.com by imo-da04.mx.aol.com (mail_out_v40_r1.5.) id 9.d59.4031ac99 (41811); Wed, 13 May 2009 03:50:20 -0400 (EDT) From: HeinerHummel@aol.com Message-ID: Date: Wed, 13 May 2009 03:50:20 EDT To: jnc@mercury.lcs.mit.edu, rrg@irtf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1242201020" X-Mailer: 9.0 SE for Windows sub 5021 X-AOL-IP: 205.188.169.202 Subject: Re: [rrg] Locator X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2009 07:49:10 -0000 -------------------------------1242201020 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable In einer eMail vom 13.05.2009 02:13:52 Westeurop=E4ische Normalzeit schrei= bt jnc@mercury.lcs.mit.edu: Ah, no. To quote RFC-1992: "A locator ... identifies a location in an internetwork. Nodes and endpoint are assigned locators. Different nodes have necessarily different locator= s. A node is assigned only one locator. Locators identify nodes and specify *where* a node is in the network. Locators do *not* specify a path to the node." I perfectly agree."Nodes and endpoint are assigned locators" can also be= read: "Nodes and endpoints are assigned attributes (eventually in addition= ?! to identifiers ) which are locators. One also needs to be aware that in this document, "node" means 'network region', not 'host/router', as it is commonly taken to mean in networking= : "A node represents a region of the physical network. The region of the network represented by a node can be as large or as small as desired: a node can represent a continent or a process running inside a host. Moreover .. a region of the network can simultaneously be represented by more than one node." I perfectly agree. However I would like to caution not to do the same kin= d of node aggregation once again as known from PNNI. (In the next section of the document, "node" is very precisely defined to= mean 'map element' - from the node/arc terminology of graph theory, since maps= are graphs - the above is just a 'starter definition'.) it sounds like TARA :-) Heiner -------------------------------1242201020 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
In einer eMail vom 13.05.2009 02:13:52 Westeurop=E4ische Normalzeit= schreibt jnc@mercury.lcs.mit.edu:
Ah, no. To quote RFC-1992:

  "A locator ... identifies a location in= an internetwork.  Nodes and endpoint
  are assigned locators.= Different nodes have necessarily different locators.
  A node is= assigned only one locator. Locators identify nodes and specify
 = *where* a node is in the network. Locators do *not* specify a path to the
  node."
 
I perfectly agree."Nodes and endpoint are assigned locators" can also= be read: "Nodes and endpoints are assigned attributes (eventually in add= ition ?! to identifiers ) which are locators.


One also needs to be aware that in this document, "node= " means 'network
region', not 'host/router', as it is commonly taken to mean= in networking:

  "A node represents a region of the physical network.  The region of the
   network represented by= a node can be as large or as small as desired: a
   node can repre= sent a continent or a process running inside a host.
   Moreover= .. a region of the network can simultaneously be represented by
 &nbs= p; more than one node."
I perfectly agree. However I would like to caution not to do the= same kind of node aggregation once again
as known from PNNI.

(In the next section of the document, "node" is very precisely defined to mean
'map element' - from the node/arc terminology of graph theory,= since maps are
graphs - the above is just a 'starter definition'.)
it sounds like TARA :-)
 
Heiner
-------------------------------1242201020-- From irtf@tonistoev.info Thu May 14 01:29:57 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6AE6228C1F7 for ; Thu, 14 May 2009 01:29:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.266 X-Spam-Level: X-Spam-Status: No, score=-1.266 tagged_above=-999 required=5 tests=[AWL=-0.526, BAYES_20=-0.74] 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 aVI9fRWtb5dC for ; Thu, 14 May 2009 01:29:56 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 955B728C1DD for ; Thu, 14 May 2009 01:29:56 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M4WLc-0001hK-LD for rrg@irtf.org; Thu, 14 May 2009 11:31:24 +0300 From: Toni Stoev To: IRTF RRG Date: Thu, 14 May 2009 11:31:22 +0300 User-Agent: KMail/1.9.9 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905141131.22465.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: [rrg] Locator: routing scalability X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2009 08:29:57 -0000 So locator may name node. And node may be host/router. Being confident routing researchers, let us go on for the routing scalability. Please answer the following question: Does locator have to facilitate routing with its structure? My answer is: yes, it must. Toni From HeinerHummel@aol.com Thu May 14 12:09:08 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4765E3A695B for ; Thu, 14 May 2009 12:09:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.098 X-Spam-Level: X-Spam-Status: No, score=-0.098 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_50=0.001, HTML_MESSAGE=0.001] 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 jAtDd09m3rBn for ; Thu, 14 May 2009 12:09:07 -0700 (PDT) Received: from imr-m08.mx.aol.com (imr-m08.mx.aol.com [64.12.138.210]) by core3.amsl.com (Postfix) with ESMTP id 7AA093A6C35 for ; Thu, 14 May 2009 12:09:07 -0700 (PDT) Received: from imo-da04.mx.aol.com (imo-da04.mx.aol.com [205.188.169.202]) by imr-m08.mx.aol.com (v107.10) with ESMTP id RELAYIN2-34a0c6ca321d; Thu, 14 May 2009 15:10:27 -0400 Received: from HeinerHummel@aol.com by imo-da04.mx.aol.com (mail_out_v40_r1.5.) id a.cc9.5094be77 (39331); Thu, 14 May 2009 15:10:18 -0400 (EDT) From: HeinerHummel@aol.com Message-ID: Date: Thu, 14 May 2009 15:10:18 EDT To: irtf@tonistoev.info, rrg@irtf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1242328218" X-Mailer: 9.0 SE for Windows sub 5021 X-AOL-IP: 205.188.169.202 Subject: Re: [rrg] Locator: routing scalability X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2009 19:09:08 -0000 -------------------------------1242328218 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable In einer eMail vom 14.05.2009 10:31:34 Westeurop=E4ische Normalzeit schrei= bt irtf@tonistoev.info: So locator may name node. And node may be host/router. Being confident routing researchers, let us go on for the routing scalability. Please answer the following question: Does locator have to facilitate routing with its structure? My answer is: yes, it must. Toni I have the same answer. Yes it must. With strategy C such that by 90 % a single table-offset (i.e. as by the = locator) retrieves the next hop. Note: GPS is state of the art. We don't live in the 1980s anymore. Heiner -------------------------------1242328218 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
In einer eMail vom 14.05.2009 10:31:34 Westeurop=E4ische Normalzeit= schreibt irtf@tonistoev.info:
So locator may name node. And node may be host/router.

Being confide= nt routing researchers, let us go on for the routing scalability.

Pl= ease answer the following question:
Does locator have to facilitate routin= g with its structure?
My answer is: yes, it must.

Toni
I have the same answer.
Yes it must.
With strategy C such that by 90 % a single table-offset (i.e. as by= the locator) retrieves the next hop.
Note: GPS is state of the art. We don't live in the 1980s anymore.
 
Heiner
-------------------------------1242328218-- From irtf@tonistoev.info Thu May 14 19:01:51 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 127413A6C5A for ; Thu, 14 May 2009 19:01:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.174 X-Spam-Level: X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[AWL=0.425, 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 EJe2L3tI7tvT for ; Thu, 14 May 2009 19:01:50 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 1ABB83A6BD5 for ; Thu, 14 May 2009 19:01:45 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M4mlX-0003HY-94 for rrg@irtf.org; Fri, 15 May 2009 05:03:15 +0300 From: Toni Stoev To: IRTF RRG Date: Fri, 15 May 2009 05:03:14 +0300 User-Agent: KMail/1.9.9 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905150503.14626.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [rrg] Locator: routing scalability X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 May 2009 02:01:51 -0000 > > Does locator have to facilitate routing with its structure? > > > > Toni > > I have the same answer. > Yes it must. > With strategy C such that by 90 % a single table-offset (i.e. as by the > locator) retrieves the next hop. > > Heiner The next hop is a neighbor node. What is the easiest case to retrieve it from locator? Locator containing it. So here's next question I have the pleasure to ask our attentive peers: Must locator structure show explicit topology/reachability/routability? My answer: Let me listen before speak. Toni From HeinerHummel@aol.com Fri May 15 01:28:59 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A280F3A6AA4 for ; Fri, 15 May 2009 01:28:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.463 X-Spam-Level: X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[AWL=0.276, BAYES_20=-0.74, HTML_MESSAGE=0.001] 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 rv3K4Lq-OAbj for ; Fri, 15 May 2009 01:28:58 -0700 (PDT) Received: from imo-d06.mx.aol.com (imo-d06.mx.aol.com [205.188.157.38]) by core3.amsl.com (Postfix) with ESMTP id 9A7CE3A6A0A for ; Fri, 15 May 2009 01:28:58 -0700 (PDT) Received: from imo-da04.mx.aol.com (imo-da04.mx.aol.com [205.188.169.202]) by imo-d06.mx.aol.com (8.14.1/8.14.1) with ESMTP id n4F8UUQY015741; Fri, 15 May 2009 04:30:30 -0400 (EDT) Received: from HeinerHummel@aol.com by imo-da04.mx.aol.com (mail_out_v40_r1.5.) id a.d49.46c7fbdc (42805); Fri, 15 May 2009 04:30:23 -0400 (EDT) From: HeinerHummel@aol.com Message-ID: Date: Fri, 15 May 2009 04:30:22 EDT To: irtf@tonistoev.info, rrg@irtf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1242376222" X-Mailer: 9.0 SE for Windows sub 5021 Subject: Re: [rrg] Locator: routing scalability X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 May 2009 08:28:59 -0000 -------------------------------1242376222 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable In einer eMail vom 15.05.2009 04:03:34 Westeurop=E4ische Normalzeit schrei= bt irtf@tonistoev.info: > > Does locator have to facilitate routing with its structure? > > > > Toni > > I have the same answer. > Yes it must. > With strategy C such that by 90 % a single table-offset (i.e. as by the= > locator) retrieves the next hop. > > Heiner The next hop is a neighbor node. What is the easiest case to retrieve it= from locator? Locator containing it. So here's next question I have the pleasure to ask our attentive peers: Must locator structure show explicit topology/reachability/routability? Toni, The locator according to TARA (strategy C) would indicate the destination's geographical square degree patch, thereof the right square= minute patch, thereof the right square second patch. This is the entire locator structure (wrt the dest.). A transit router whose own square degree patch doesn't match the destination's square degree patch would use that one to offset a table for= retrieving the next hop. Otherwise one could say: proceed as well with the square minute/ square = second part of the locator so that only one single table-offset is needed= in every case (plus up to three compares). However this is also a question= of memory optimization. That's why I once backed up by saying : otherwise= it will take three table lookups. Heiner -------------------------------1242376222 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
In einer eMail vom 15.05.2009 04:03:34 Westeurop=E4ische Normalzeit= schreibt irtf@tonistoev.info:
> > Does locator have to facilitate routing with its structure?
>= >
> > Toni
>
> I have the same answer.
> Yes= it must.
> With strategy C such that by 90 % a single table-offset (i= .e. as by the 
> locator) retrieves the next hop.
>
>= Heiner

The next hop is a neighbor node. What is the easiest case= to retrieve it from locator? Locator containing it.
So here's next quest= ion I have the pleasure to ask our attentive peers:
Must locator structure= show explicit topology/reachability/routability?
Toni,
The locator  according to TARA (strategy C) would indicate the= destination's geographical square degree patch, thereof the right square= minute patch, thereof the right square second patch. This is the entire locator= structure (wrt the dest.).
A transit router whose own square degree patch doesn't match the destination's square degree patch would use that one to offset a table for= retrieving the next hop.
Otherwise one could say: proceed as well with the square minute/ squa= re second part of the locator so that only one  single table-offset is= needed in  every case (plus up to three compares). However this is also= a question of memory optimization. That's why I once backed up by saying := otherwise it will take three table lookups.
 
Heiner

 
-------------------------------1242376222-- From paul@jakma.org Fri May 15 14:33:45 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BB6F3A6A57 for ; Fri, 15 May 2009 14:33:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.549 X-Spam-Level: X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 k82emSkbCiC5 for ; Fri, 15 May 2009 14:33:44 -0700 (PDT) Received: from hibernia.jakma.org (cl-9.dub-01.ie.sixxs.net [IPv6:2001:770:100:8::2]) by core3.amsl.com (Postfix) with ESMTP id BB4543A69C5 for ; Fri, 15 May 2009 14:33:43 -0700 (PDT) Received: from melandri.gla.jakma.org (melandri.jakma.org [81.168.24.37]) (authenticated bits=0) by hibernia.jakma.org (8.14.3/8.14.3) with ESMTP id n4FLYuG7018665 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 May 2009 22:35:10 +0100 Date: Fri, 15 May 2009 22:34:56 +0100 (BST) From: Paul Jakma To: Toni Stoev In-Reply-To: <200905141131.22465.irtf@tonistoev.info> Message-ID: References: <200905141131.22465.irtf@tonistoev.info> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) Mail-Copies-To: paul@jakma.org Mail-Followup-To: paul@jakma.org X-NSA: al aqsar fluffy jihad cute musharef kittens jet-A1 ear avgas wax ammonium bad qran dog inshallah allah al-akbar martyr iraq hammas hisballah rabin ayatollah korea revolt pelvix mustard gas x-ray british airways washington peroxide cool MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.1.1 (hibernia.jakma.org [212.17.55.49]); Fri, 15 May 2009 22:35:12 +0100 (IST) Cc: IRTF RRG Subject: Re: [rrg] Locator: routing scalability X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 May 2009 21:33:45 -0000 On Thu, 14 May 2009, Toni Stoev wrote: > Does locator have to facilitate routing with its structure? > My answer is: yes, it must. I have a question, a stupid one probably... Is the following thinking of mine correct?: If we encode routing information into the locator somehow, then this implies the 2 are tied together, and that (at least) the initial top-level hierarchy of internet routing is fixed for the life-time of the locator. So this implies either one or more of: - that the lifetime of locators be short, and that they are re-calculated/re-assigned frequently enough to have a sufficient level of reachability between hosts on the internet. (e.g. imagine a scheme that assigned locators empirically, by examining the structure of the internet and calculating a spanning-tree that approximated a power-law distribution as good as possible and then assigning locators in an according fashion, thus maximising the aggregation of routing information. I think there may be papers describing such things, but I'm not sure there are RRG proposals ???). - fairly long-lived, indeed static locator assignments. This implies a quite broad and flat, top-level routing table. This is basically what we have today, if ASes advertised just one prefix. Proposals under this model generally split routing into a 2-tier system: the flat, top-level routing table + a secondary table of networks behind the top-level locators (either aggregated locators, or remapped/tunneled somehow) Is this right so far? If so, and if the prevailing proposals so far are of the static top-level kind, then do know if a flat top-level is sufficiently scalable? Is there any data/work on how fast this top-level might grow? To what extent is the AS growth reflective of how that top-level might grow? To what extent is the transit-AS growth reflective of it? I ask because AS growth might not be linear: http://www.potaroo.net/tools/asn32/ though transit-AS growth is unclear (it doesn't grow much in fact, so its perhaps impossible to get a trend from it): http://www.potaroo.net/ispcol/2009-03/bgp2008.html Basically, what I wonder is whether a static top-level locator->routing mapping is sufficient to meet the scaleability requirement? If it is not, then facilitating routing with the locator is just a delaying tactic - a more dynamic system would eventually be necessary. If it is sufficient, great, of course - any dynamic system would by definition be more complex. (There may be ways of statically assigning locators according to some kind of power-law distribution - but this means impressing some kind of order onto ISPs, which probably isn't socio-politically tractable). regards, -- Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A Fortune: Neutrinos are into physicists. From irtf@tonistoev.info Sun May 17 03:30:26 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0917A3A69B1 for ; Sun, 17 May 2009 03:30:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.891 X-Spam-Level: X-Spam-Status: No, score=-0.891 tagged_above=-999 required=5 tests=[AWL=-0.892, BAYES_50=0.001] 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 kupZECJ0SWkQ for ; Sun, 17 May 2009 03:30:24 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 658E23A6822 for ; Sun, 17 May 2009 03:30:24 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M5det-0006fc-Hy for rrg@irtf.org; Sun, 17 May 2009 13:31:55 +0300 From: Toni Stoev Date: Sun, 17 May 2009 13:31:54 +0300 User-Agent: KMail/1.9.9 References: <200905141131.22465.irtf@tonistoev.info> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline To: IRTF RRG Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200905171331.54425.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [rrg] Locator: routing scalability X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 May 2009 10:30:26 -0000 Paul, have my regards for going deep into the matter. See my comments inline. On Saturday 16 May 2009 00:34:56 Paul Jakma sent: > On Thu, 14 May 2009, Toni Stoev wrote: > > > Does locator have to facilitate routing with its structure? > > My answer is: yes, it must. > > I have a question, a stupid one probably... Is the following thinking > of mine correct?: > > If we encode routing information into the locator somehow, then this > implies the 2 are tied together, and that (at least) the initial > top-level hierarchy of internet routing is fixed for the life-time of > the locator. This shall be backwards when using locator for intra-domain routing (and AS paths for inter-domain routing). Then locator's tying is with its routing domain (AS). And the intra-domain location-naming/routing hierarchy needs just the AS number as its top-level. > So this implies either one or more of: > > - that the lifetime of locators be short, and that they are > re-calculated/re-assigned frequently enough to have a sufficient > level of reachability between hosts on the internet. My vision is that node reachability has to be shown by locator. Then lifetime of locators has to be relevant to that reachability. > (e.g. imagine a scheme that assigned locators empirically, by > examining the structure of the internet and calculating a > spanning-tree that approximated a power-law distribution > as good as possible and then assigning locators in an according > fashion, thus maximising the aggregation of routing information. > > I think there may be papers describing such things, but I'm not > sure there are RRG proposals ???). > > - fairly long-lived, indeed static locator assignments. This implies > a quite broad and flat, top-level routing table. This is basically > what we have today, if ASes advertised just one prefix. > > Proposals under this model generally split routing into a 2-tier > system: the flat, top-level routing table + a secondary table of > networks behind the top-level locators (either aggregated locators, > or remapped/tunneled somehow) > > Is this right so far? > > If so, and if the prevailing proposals so far are of the static > top-level kind, then do know if a flat top-level is sufficiently > scalable? Is there any data/work on how fast this top-level might > grow? To what extent is the AS growth reflective of how that > top-level might grow? To what extent is the transit-AS growth > reflective of it? > > I ask because AS growth might not be linear: > > http://www.potaroo.net/tools/asn32/ > > though transit-AS growth is unclear (it doesn't grow much in fact, so > its perhaps impossible to get a trend from it): > > http://www.potaroo.net/ispcol/2009-03/bgp2008.html Paul, please keep helping with AS growth revision. > Basically, what I wonder is whether a static top-level > locator->routing mapping is sufficient to meet the scaleability > requirement? > > If it is not, then facilitating routing with the locator is just a > delaying tactic - a more dynamic system would eventually be > necessary. > > If it is sufficient, great, of course - any dynamic system would by > definition be more complex. > > (There may be ways of statically assigning locators according to some > kind of power-law distribution - but this means impressing some kind > of order onto ISPs, which probably isn't socio-politically > tractable). > > regards, Reconsider, Toni From irtf@tonistoev.info Mon May 18 12:56:19 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D84D3A6ABF for ; Mon, 18 May 2009 12:56:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.951 X-Spam-Level: X-Spam-Status: No, score=-0.951 tagged_above=-999 required=5 tests=[AWL=-0.766, BAYES_40=-0.185] 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 yFzCHfcut1Ny for ; Mon, 18 May 2009 12:56:19 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 491303A7036 for ; Mon, 18 May 2009 12:56:00 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M68xo-0002jP-BG for rrg@irtf.org; Mon, 18 May 2009 22:57:32 +0300 From: Toni Stoev To: IRTF RRG Date: Mon, 18 May 2009 22:57:27 +0300 User-Agent: KMail/1.9.9 References: <200905150503.14626.irtf@tonistoev.info> In-Reply-To: <200905150503.14626.irtf@tonistoev.info> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905182257.28002.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [rrg] Locator: routing scalability X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2009 19:56:19 -0000 On Friday 15 May 2009 05:03:14 Toni Stoev sent: > > > Does locator have to facilitate routing with its structure? > > > > > > Toni > > > > I have the same answer. > > Yes it must. > > With strategy C such that by 90 % a single table-offset (i.e. as by the > > locator) retrieves the next hop. > > > > Heiner > > The next hop is a neighbor node. What is the easiest case to retrieve it from locator? Locator containing it. > So here's next question I have the pleasure to ask our attentive peers: > Must locator structure show explicit topology/reachability/routability? > > My answer: Let me listen before speak. > > Toni > My opinion is that locator must contain next hops along a path from a root router to a node within a routing domain. Thus locator will be a safe way for a packet en route to its destination, within locator's routing domain. And especially, being quite relevant to topology, locator will natively provide intra-domain routing scalability. Furthermore, locator being an intra-domain asset, locator quantity growth will be clearly decoupled from inter-domain routing. Consider, Toni Stoev From Fred.L.Templin@boeing.com Mon May 18 16:25:03 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE2643A6E81 for ; Mon, 18 May 2009 16:25:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.212 X-Spam-Level: X-Spam-Status: No, score=-6.212 tagged_above=-999 required=5 tests=[AWL=0.387, 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 2X8A55syEzY5 for ; Mon, 18 May 2009 16:25:03 -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 E91573A691E for ; Mon, 18 May 2009 16:25:02 -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 n4INQUk9015557 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 18 May 2009 18:26:32 -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 n4INQUVv023947 for ; Mon, 18 May 2009 18:26:30 -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 n4INQPq2023853 for ; Mon, 18 May 2009 18:26:29 -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); Mon, 18 May 2009 16:26:25 -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: Mon, 18 May 2009 16:26:24 -0700 Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A105F43829@XCH-NW-7V2.nw.nos.boeing.com> In-Reply-To: <200905182257.28002.irtf@tonistoev.info> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: RANGER(S) Thread-Index: AcnX8v/+rknQlzRzRrKBYK4juEO+AQAGgRkg References: <200905150503.14626.irtf@tonistoev.info> <200905182257.28002.irtf@tonistoev.info> From: "Templin, Fred L" To: "IRTF RRG" X-OriginalArrivalTime: 18 May 2009 23:26:25.0097 (UTC) FILETIME=[0FAEF390:01C9D810] Subject: [rrg] RANGER(S) X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2009 23:25:03 -0000 There hasn't been much new here in the way of proposals lately, so I thought I'd take a moment to announce "RANGER Scenarios" and its precursor "RANGER": http://tools.ietf.org/html/draft-russert-rangers http://tools.ietf.org/html/draft-templin-ranger RANGERS picks up where RANGER left off; it not only completes the architectural framework, but also highlights the myriad use cases for which the architecture applies. It cannot really be claimed that this work is "new" (far from it!), but in our experience RANGER(S) is the only proposal with a consistent architectural framework that applies recursively in a "network-of-networks" fashion from the global Internet core all the way outward to even the simplest of edge networks. Indeed, the limiting factor for recursion is a singleton node and its associated devices.=20 Please take a moment to review the proposal and send comments. Tony and Lixia - can we have this work added to the wiki page as an active rrg proposal? Thanks - Fred fred.l.templin@boeing.com=20 From HeinerHummel@aol.com Tue May 19 00:26:59 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C8F328C13B for ; Tue, 19 May 2009 00:26:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.011 X-Spam-Level: X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[AWL=0.173, BAYES_40=-0.185, HTML_MESSAGE=0.001] 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 dQ4FYIzGPFe4 for ; Tue, 19 May 2009 00:26:58 -0700 (PDT) Received: from imr-d01.mx.aol.com (imr-d01.mx.aol.com [205.188.157.39]) by core3.amsl.com (Postfix) with ESMTP id A8D4228C136 for ; Tue, 19 May 2009 00:26:58 -0700 (PDT) Received: from imo-ma01.mx.aol.com (imo-ma01.mx.aol.com [64.12.78.136]) by imr-d01.mx.aol.com (v107.10) with ESMTP id RELAYIN2-34a125f95114; Tue, 19 May 2009 03:28:21 -0400 Received: from HeinerHummel@aol.com by imo-ma01.mx.aol.com (mail_out_v40_r1.5.) id p.d49.472abe45 (48600); Tue, 19 May 2009 03:28:15 -0400 (EDT) From: HeinerHummel@aol.com Message-ID: Date: Tue, 19 May 2009 03:31:23 EDT To: Fred.L.Templin@boeing.com, rrg@irtf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1242718283" X-Mailer: 9.0 SE for Windows sub 5021 X-AOL-IP: 64.12.78.136 Subject: Re: [rrg] RANGER(S) X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 07:26:59 -0000 -------------------------------1242718283 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable In einer eMail vom 19.05.2009 01:26:57 Westeurop=E4ische Normalzeit schrei= bt Fred.L.Templin@boeing.com: but in our experience RANGER(S) is the only proposal with a consistent architectural framework that applies recursively in a "network-of-networks" fashion from the global Internet core all the way outward to even the simplest of edge networks. I have never understood either that inter- and intra-domain routing architectures have to be such orthogonal. So whatever I proposed or supported so far was aiming to a consistent architectural framework, too. Routing, which is not based on address summarization, would make sense inside of intra-domain-networks as well. Heiner -------------------------------1242718283 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
In einer eMail vom 19.05.2009 01:26:57 Westeurop=E4ische Normalzeit= schreibt Fred.L.Templin@boeing.com:
but in our
experience RANGER(S) is the only proposal with a consistent
architectural framework that applies recursively in a
"network-of-networks" fashion from the global Internet core
all= the way outward to even the simplest of edge networks.
I have never understood either that inter- and intra-domain routing= architectures have to be such orthogonal.
So whatever I proposed or supported so far was aiming to a consi= stent architectural framework, too.
Routing, which is not based on address summarization, would make sens= e inside of intra-domain-networks as well.
 
Heiner
-------------------------------1242718283-- From Fred.L.Templin@boeing.com Tue May 19 09:33:14 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1ABA93A69E4 for ; Tue, 19 May 2009 09:33:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.004 X-Spam-Level: X-Spam-Status: No, score=-6.004 tagged_above=-999 required=5 tests=[AWL=0.279, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315] 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 PnJOVA2op-q9 for ; Tue, 19 May 2009 09:33:11 -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 57D4D3A68B0 for ; Tue, 19 May 2009 09:33:11 -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 n4JGYiWP004487 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 19 May 2009 11:34:45 -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 n4JGYiuf003618; Tue, 19 May 2009 11:34:44 -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 n4JGYiZC003591; Tue, 19 May 2009 11:34:44 -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, 19 May 2009 09:34:44 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9D89F.B6BE8EE9" Date: Tue, 19 May 2009 09:34:42 -0700 Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A105F43B01@XCH-NW-7V2.nw.nos.boeing.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [rrg] RANGER(S) Thread-Index: AcnYU2tlKwyfUJtsQ6+lOP42lqOCfAAStFwg References: From: "Templin, Fred L" To: , X-OriginalArrivalTime: 19 May 2009 16:34:44.0520 (UTC) FILETIME=[B767C280:01C9D89F] Subject: Re: [rrg] RANGER(S) X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 16:33:14 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9D89F.B6BE8EE9 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Heiner, =20 > I have never understood either that inter- and intra-domain routing = architectures have to be such orthogonal. > So whatever I proposed or supported so far was aiming to a consistent = architectural framework, too. > Routing, which is not based on address summarization, would make sense = inside of intra-domain-networks as well. =20 Do these other approaches show how they recurse from the Internet core all the way to a singleton node as the limiting factor for recursion - = or even to virtual networks within a singleton node? =20 Do the other approaches provide for discovery and utilization of = multiple border routers? =20 Do they have fully-articulated specifications for automatic EID and RLOC address configuration? =20 Do they support multihoming? =20 Provider-independent addressing? =20 IPv6 deployment? =20 Traffic engineering? =20 Secure redirection? =20 Ingress filtering? =20 What about mobility? =20 MTU handling for tunnels? =20 _Do the other approaches have their base mechanisms widely deployed in shipping implementations for many years, and with many millions of users?_ =20 Is maturity important to this group? What about completeness? =20 Fred fred.l.templin@boeing.com=20 =20 =20 ________________________________ From: HeinerHummel@aol.com [mailto:HeinerHummel@aol.com]=20 Sent: Tuesday, May 19, 2009 12:31 AM To: Templin, Fred L; rrg@irtf.org Subject: Re: [rrg] RANGER(S) =20 In einer eMail vom 19.05.2009 01:26:57 Westeurop=E4ische Normalzeit = schreibt Fred.L.Templin@boeing.com: but in our experience RANGER(S) is the only proposal with a consistent architectural framework that applies recursively in a "network-of-networks" fashion from the global Internet core all the way outward to even the simplest of edge networks. I have never understood either that inter- and intra-domain routing = architectures have to be such orthogonal. So whatever I proposed or supported so far was aiming to a consistent = architectural framework, too. Routing, which is not based on address summarization, would make sense = inside of intra-domain-networks as well. =20 Heiner ------_=_NextPart_001_01C9D89F.B6BE8EE9 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Heiner,

 

> I have never understood = either that inter- and intra-domain routing architectures have to be such = orthogonal.

> So whatever I proposed or = supported so far was aiming to a consistent architectural framework, = too.

> Routing, which is not based = on address summarization, would make sense inside of intra-domain-networks = as well.

 

Do these other approaches show how = they recurse from the Internet core

all the way to a singleton node as = the limiting factor for recursion – or even

to virtual networks within a = singleton node?

 

Do the other approaches provide = for discovery and utilization of multiple

border routers?

 

Do they have fully-articulated specifications for automatic EID and RLOC

address = configuration?

 

Do they support = multihoming?

 

Provider-independent = addressing?

 

IPv6 deployment?

 

Traffic = engineering?

 

Secure = redirection?

 

Ingress = filtering?

 

What about = mobility?

 

MTU handling for = tunnels?

 

_Do the other approaches have = their base mechanisms widely deployed

in shipping implementations for = many years, and with many millions of

users?_

 

Is maturity important to this = group? What about completeness?

 

Fred

fred.l.templin@boeing.com =

 

 


From: HeinerHummel@aol.com [mailto:HeinerHummel@aol.com]
Sent: Tuesday, May 19, = 2009 12:31 AM
To: Templin, Fred L; = rrg@irtf.org
Subject: Re: [rrg] = RANGER(S)

 

In einer eMail vom 19.05.2009 = 01:26:57 Westeurop=E4ische Normalzeit schreibt = Fred.L.Templin@boeing.com:

but in our
experience RANGER(S) is the only proposal with a consistent
architectural framework that applies recursively in a
"network-of-networks" fashion from the global Internet = core
all the way outward to even the simplest of edge = networks.

I have never understood either = that inter- and intra-domain routing architectures have to be such = orthogonal.

So whatever I proposed or = supported so far was aiming to a consistent architectural framework, = too.

Routing, which is not based on = address summarization, would make sense inside of intra-domain-networks as = well.

 

Heiner

------_=_NextPart_001_01C9D89F.B6BE8EE9-- From HeinerHummel@aol.com Tue May 19 12:21:25 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CEF343A6E16 for ; Tue, 19 May 2009 12:21:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.251 X-Spam-Level: X-Spam-Status: No, score=-1.251 tagged_above=-999 required=5 tests=[AWL=1.032, BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_MILLIONSOF=0.315] 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 G+xyWI53HSUZ for ; Tue, 19 May 2009 12:21:22 -0700 (PDT) Received: from imr-d04.mx.aol.com (imr-d04.mx.aol.com [205.188.157.42]) by core3.amsl.com (Postfix) with ESMTP id 87CCF3A6973 for ; Tue, 19 May 2009 12:21:21 -0700 (PDT) Received: from imo-da01.mx.aol.com (imo-da01.mx.aol.com [205.188.169.199]) by imr-d04.mx.aol.com (v107.10) with ESMTP id RELAYIN1-24a1306d11e5; Tue, 19 May 2009 15:21:53 -0400 Received: from HeinerHummel@aol.com by imo-da01.mx.aol.com (mail_out_v40_r1.5.) id p.be5.5460fad5 (42808); Tue, 19 May 2009 15:21:48 -0400 (EDT) From: HeinerHummel@aol.com Message-ID: Date: Tue, 19 May 2009 15:21:47 EDT To: Fred.L.Templin@boeing.com, rrg@irtf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1242760907" X-Mailer: 9.0 SE for Windows sub 5021 X-AOL-IP: 205.188.169.199 Subject: Re: [rrg] RANGER(S) X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 19:21:25 -0000 -------------------------------1242760907 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 RnJlZCwKb25lIGJ5IG9uZSwgc2VlIGluc2lkZS4KSGVpbmVyCiAKIApJbiBlaW5lciBlTWFpbCB2 b20gMTkuMDUuMjAwOSAxODozNTowMCBXZXN0ZXVyb3DDpGlzY2hlIE5vcm1hbHplaXQgc2NocmVp YnQgIApGcmVkLkwuVGVtcGxpbkBib2VpbmcuY29tOgoKIApIZWluZXIsIAo+IEkgaGF2ZSBuZXZl ciAgdW5kZXJzdG9vZCBlaXRoZXIgdGhhdCBpbnRlci0gYW5kIGludHJhLWRvbWFpbiByb3V0aW5n IAphcmNoaXRlY3R1cmVzIGhhdmUgdG8gIGJlIHN1Y2ggb3J0aG9nb25hbC4gCj4gU28gd2hhdGV2 ZXIgSSAgcHJvcG9zZWQgb3Igc3VwcG9ydGVkIHNvIGZhciB3YXMgYWltaW5nIHRvIGEgY29uc2lz dGVudCAKYXJjaGl0ZWN0dXJhbCAgZnJhbWV3b3JrLCB0b28uIAo+IFJvdXRpbmcsIHdoaWNoICBp cyBub3QgYmFzZWQgb24gYWRkcmVzcyBzdW1tYXJpemF0aW9uLCB3b3VsZCBtYWtlIHNlbnNlIApp bnNpZGUgb2YgIGludHJhLWRvbWFpbi1uZXR3b3JrcyBhcyB3ZWxsLiAKRG8gdGhlc2Ugb3RoZXIg IGFwcHJvYWNoZXMgc2hvdyBob3cgdGhleSByZWN1cnNlIGZyb20gdGhlIEludGVybmV0IGNvcmUg CmFsbCB0aGUgd2F5IHRvIGEgIHNpbmdsZXRvbiBub2RlIGFzIHRoZSBsaW1pdGluZyBmYWN0b3Ig Zm9yIHJlY3Vyc2lvbiDigJMgb3IgIApldmVuIAp0byB2aXJ0dWFsIG5ldHdvcmtzICB3aXRoaW4g YSBzaW5nbGV0b24gbm9kZT8KCkFianVyaW5nIHRoZSBhZGRyZXNzIGFzdW1tYXJpemF0aW9uIHBh cmFkaWdtIGluIGludGVyLWRvbWFpbiByb3V0aW5nLCB3aHkgIApzaG91bGQgSSBzdGljayB0byBp dCBpbiBpbnRyYS1kb21haW4gcm91dGluZyA/Oi0oIEhvd2V2ZXIgdGhlcmUsIHRoZSBuZWVkIApm b3IgYSAgZnVuZGFtZW50YWwgY2hhbmdlIGlzbid0IGFzIGltbWVuc2UuCgpEbyB0aGUgb3RoZXIg IGFwcHJvYWNoZXMgcHJvdmlkZSBmb3IgZGlzY292ZXJ5IGFuZCB1dGlsaXphdGlvbiBvZiBtdWx0 aXBsZSAKYm9yZGVyICByb3V0ZXJzPwouLi4gYm9yZGVyIHJvdXRlcnMgYXMgdW5kZXJzdG9vZCBi eSBlYWNoIGluZGl2aWR1YWwgYXBwcm9hY2guIEJ1dCB0aGUgIAphbnN3ZXIgaXMgeWVzLgogCgpE byB0aGV5IGhhdmUgIGZ1bGx5LWFydGljdWxhdGVkIHNwZWNpZmljYXRpb25zIGZvciBhdXRvbWF0 aWMgRUlEIGFuZCBSTE9DIAphZGRyZXNzICBjb25maWd1cmF0aW9uPwpUaGVyZSBpcyBubyBuZWVk IGZvciBzdWNoIHRoaW5ncy4gIAoKRG8gdGhleSBzdXBwb3J0ICBtdWx0aWhvbWluZz8KV2hhdCBh ICBxdWVzdGlvbiAhIE9mIGNvdXJzZSwgeWVzLgoKUHJvdmlkZXItaW5kZXBlbmRlbnQgIGFkZHJl c3Npbmc/ClBJLSAgYW5kIFBBLSBpbmRlcGVuZGVudCBhZGRyZXNzaW5nLCBzbyB0byBzcGVhay4K CklQdjYgIGRlcGxveW1lbnQ/ClllcywgYW5kIHdoYXRldmVyIGVsc2UuCgpUcmFmZmljICBlbmdp bmVlcmluZz8KSXQgd291bGQgcHJvdmlkZSBhIGxhcmdlIG1lYWRvdyBmb3IgVEUsIG5ldmVyIGV2 ZXIgc2VlbiBiZWZvcmUuClNlY3VyZSAgcmVkaXJlY3Rpb24/IApwcm9taXNlZC4gCkluZ3Jlc3Mg IGZpbHRlcmluZz8KR2l2ZW4gSSBrbm93IHRoZSB0b3BvbG9neSBhbmQgbm90IG9ubHkgMzAwIDAw MCByb3V0ZXMsIHdoeSBzaG91bGQgaW5ncmVzcyAgCmZpbHRlcmluZyBub3QgYmUgcG9zc2libGU/ ClllcywgaXQgY2Fubm90IGJlIGRvbmUgYXMgZm9sa3MgYXJlIHVzZWQgdG8uCgpXaGF0IGFib3V0 ICBtb2JpbGl0eT8KWW91J2xsIGJldC4gV2l0aG91dCBnZW9ncmFwaGljYWwgY29vcmRpbmF0ZXMs ICBtb2JpbGl0eSB3b3VsZG4ndCAgYmUuCgpNVFUgaGFuZGxpbmcgZm9yICB0dW5uZWxzPwpZZXMs IEkgd291bGQgYWxzbyBuZWVkIHNvbWUgb3V0ZXIgaGVhZGVyLCBqdXN0IGxpa2UgTElTUC4KQnV0 IHRoZXJlIGlzIGFsc28gYW4gYWx0ZXJuYXRpdmU6IFJlYWxpemF0aW9uIGluc2lkZSBsYXllciAy LiBUaGlzIHdvdWxkICAKc2hpZnQgdGhlIHJvdXRpbmcgYXJjaHRpdGVjdHVyZSBmcm9tIElFVEYg dG8gSUVFRS4gVGhpbmsgYWJvdXQgaXQgIQpEbyB0aGUgb3RoZXIgIGFwcHJvYWNoZXMgaGF2ZSB0 aGVpciBiYXNlIG1lY2hhbmlzbXMgd2lkZWx5IGRlcGxveWVkIAppbiBzaGlwcGluZyAgaW1wbGVt ZW50YXRpb25zIGZvciBtYW55IHllYXJzLCBhbmQgd2l0aCBtYW55IG1pbGxpb25zIG9mIAp1c2Vy cz9fCldoYXQgaWYgeW91IGRvbid0IG5lZWQgaHVnZSBjb3JlIHJvdXRlcnMgYW55bW9yZSA/CgpJ cyBtYXR1cml0eSAgaW1wb3J0YW50IHRvIHRoaXMgZ3JvdXA/IFdoYXQgYWJvdXQgIGNvbXBsZXRl bmVzcz8KV2hhdCBhYm91dCBnb2luZyBuZXcgcGF0aHMgZm9yIHRoaXMgZ3JvdXAgPwoKRnJlZCAK ZnJlZC5sLnRlbXBsaW5AYm9laW5nLmNvbSAgIAogCiAKICAKX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fCiAKRnJvbTogIEhlaW5lckh1bW1lbEBhb2wuY29tIFttYWlsdG86SGVp bmVySHVtbWVsQGFvbC5jb21dIApTZW50OiBUdWVzZGF5LCBNYXkgMTksIDIwMDkgMTI6MzEgIEFN ClRvOiBUZW1wbGluLCBGcmVkIEw7ICBycmdAaXJ0Zi5vcmcKU3ViamVjdDogUmU6ICBbcnJnXSBS QU5HRVIoUykKIAogCkluIGVpbmVyIGVNYWlsIHZvbSAgMTkuMDUuMjAwOSAwMToyNjo1NyBXZXN0 ZXVyb3DDpGlzY2hlIE5vcm1hbHplaXQgc2NocmVpYnQgCiBGcmVkLkwuVGVtcGxpbkBib2Vpbmcu Y29tOgoKYnV0IGluICBvdXIKZXhwZXJpZW5jZSBSQU5HRVIoUykgaXMgdGhlIG9ubHkgcHJvcG9z YWwgd2l0aCBhICBjb25zaXN0ZW50CmFyY2hpdGVjdHVyYWwgZnJhbWV3b3JrIHRoYXQgYXBwbGll cyByZWN1cnNpdmVseSBpbiAgYQoibmV0d29yay1vZi1uZXR3b3JrcyIgZmFzaGlvbiBmcm9tIHRo ZSBnbG9iYWwgSW50ZXJuZXQgY29yZQphbGwgdGhlICB3YXkgb3V0d2FyZCB0byBldmVuIHRoZSBz aW1wbGVzdCBvZiBlZGdlICBuZXR3b3Jrcy4KCiAKSSBoYXZlIG5ldmVyICB1bmRlcnN0b29kIGVp dGhlciB0aGF0IGludGVyLSBhbmQgaW50cmEtZG9tYWluIHJvdXRpbmcgCmFyY2hpdGVjdHVyZXMg aGF2ZSB0byAgYmUgc3VjaCBvcnRob2dvbmFsLgogClNvIHdoYXRldmVyIEkgIHByb3Bvc2VkIG9y IHN1cHBvcnRlZCBzbyBmYXIgd2FzIGFpbWluZyB0byBhIGNvbnNpc3RlbnQgCmFyY2hpdGVjdHVy YWwgIGZyYW1ld29yaywgdG9vLgogClJvdXRpbmcsIHdoaWNoIGlzICBub3QgYmFzZWQgb24gYWRk cmVzcyBzdW1tYXJpemF0aW9uLCB3b3VsZCBtYWtlIHNlbnNlIAppbnNpZGUgb2YgIGludHJhLWRv bWFpbi1uZXR3b3JrcyBhcyB3ZWxsLgogCgogCkhlaW5lcgoKCgogCg== -------------------------------1242760907 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4KPEhUTUw+PEhFQUQ+CjxNRVRBIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlIGNvbnRlbnQ9 InRleHQvaHRtbDsgY2hhcnNldD1VVEYtOCI+CjxNRVRBIGNvbnRlbnQ9Ik1TSFRNTCA2LjAwLjYw MDAuMTY4MjUiIG5hbWU9R0VORVJBVE9SPjwvSEVBRD4KPEJPRFkgaWQ9cm9sZV9ib2R5IHN0eWxl PSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiAjMDAwMDAwOyBGT05ULUZBTUlMWTogQXJpYWwiIApi b3R0b21NYXJnaW49NyBsZWZ0TWFyZ2luPTcgdG9wTWFyZ2luPTcgcmlnaHRNYXJnaW49Nz48Rk9O VCBpZD1yb2xlX2RvY3VtZW50IApmYWNlPUFyaWFsIGNvbG9yPSMwMDAwMDAgc2l6ZT0yPgo8RElW PkZyZWQsPC9ESVY+CjxESVY+b25lIGJ5IG9uZSwgc2VlIGluc2lkZS48L0RJVj4KPERJVj5IZWlu ZXI8L0RJVj4KPERJVj4mbmJzcDs8L0RJVj4KPERJVj4mbmJzcDs8L0RJVj4KPERJVj5JbiBlaW5l ciBlTWFpbCB2b20gMTkuMDUuMjAwOSAxODozNTowMCBXZXN0ZXVyb3DDpGlzY2hlIE5vcm1hbHpl aXQgc2NocmVpYnQgCkZyZWQuTC5UZW1wbGluQGJvZWluZy5jb206PC9ESVY+CjxCTE9DS1FVT1RF IApzdHlsZT0iUEFERElORy1MRUZUOiA1cHg7IE1BUkdJTi1MRUZUOiA1cHg7IEJPUkRFUi1MRUZU OiBibHVlIDJweCBzb2xpZCI+PEZPTlQgCiAgc3R5bGU9IkJBQ0tHUk9VTkQtQ09MT1I6IHRyYW5z cGFyZW50IiBmYWNlPUFyaWFsIGNvbG9yPSMwMDAwMDAgc2l6ZT0yPgogIDxESVYgY2xhc3M9U2Vj dGlvbjE+CiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9YmxhY2sg c2l6ZT0yPjxTUEFOIAogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9O VC1GQU1JTFk6IEFyaWFsIj5IZWluZXIsPC9TUEFOPjwvRk9OVD48L1A+CiAgPFAgY2xhc3M9TXNv Tm9ybWFsPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9YmxhY2sgc2l6ZT0yPjxTUEFOIAogIHN0eWxl PSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj48L1NQ QU4+PC9GT05UPiZuYnNwOzwvUD4KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PEZPTlQgZmFjZT1Bcmlh bCBjb2xvcj1ibGFjayBzaXplPTI+PFNQQU4gCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09M T1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwiPiZndDsgSSBoYXZlIG5ldmVyIAogIHVuZGVy c3Rvb2QgZWl0aGVyIHRoYXQgaW50ZXItIGFuZCBpbnRyYS1kb21haW4gcm91dGluZyBhcmNoaXRl Y3R1cmVzIGhhdmUgdG8gCiAgYmUgc3VjaCBvcnRob2dvbmFsLjwvU1BBTj48L0ZPTlQ+PC9QPgog IDxQIGNsYXNzPU1zb05vcm1hbD48Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPWJsYWNrIHNpemU9Mj48 U1BBTiAKICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZ OiBBcmlhbCI+Jmd0OyBTbyB3aGF0ZXZlciBJIAogIHByb3Bvc2VkIG9yIHN1cHBvcnRlZCBzbyBm YXImbmJzcDt3YXMgYWltaW5nIHRvIGEgY29uc2lzdGVudCBhcmNoaXRlY3R1cmFsIAogIGZyYW1l d29yaywgdG9vLjwvU1BBTj48L0ZPTlQ+PC9QPgogIDxQIGNsYXNzPU1zb05vcm1hbD48Rk9OVCBm YWNlPUFyaWFsIGNvbG9yPWJsYWNrIHNpemU9Mj48U1BBTiAKICBzdHlsZT0iRk9OVC1TSVpFOiAx MHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+Jmd0OyBSb3V0aW5nLCB3aGlj aCAKICBpcyBub3QgYmFzZWQgb24gYWRkcmVzcyBzdW1tYXJpemF0aW9uLCB3b3VsZCBtYWtlIHNl bnNlIGluc2lkZSBvZiAKICBpbnRyYS1kb21haW4tbmV0d29ya3MgYXMgd2VsbC48L1NQQU4+PC9G T05UPjwvUD4KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj1ibGFj ayBzaXplPTI+PFNQQU4gCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBG T05ULUZBTUlMWTogQXJpYWwiPjwvU1BBTj48L0ZPTlQ+Jm5ic3A7PC9QPgogIDxQIGNsYXNzPU1z b05vcm1hbD48Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPWJsYWNrIHNpemU9Mj48U1BBTiAKICBzdHls ZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+RG8g dGhlc2Ugb3RoZXIgCiAgYXBwcm9hY2hlcyBzaG93IGhvdyB0aGV5IHJlY3Vyc2UgZnJvbSB0aGUg SW50ZXJuZXQgY29yZTwvU1BBTj48L0ZPTlQ+PC9QPgogIDxQIGNsYXNzPU1zb05vcm1hbD48Rk9O VCBmYWNlPUFyaWFsIGNvbG9yPWJsYWNrIHNpemU9Mj48U1BBTiAKICBzdHlsZT0iRk9OVC1TSVpF OiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+YWxsIHRoZSB3YXkgdG8g YSAKICBzaW5nbGV0b24gbm9kZSBhcyB0aGUgbGltaXRpbmcgZmFjdG9yIGZvciByZWN1cnNpb24g 4oCTIG9yIApldmVuPC9TUEFOPjwvRk9OVD48L1A+CiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxGT05U IGZhY2U9QXJpYWwgY29sb3I9YmxhY2sgc2l6ZT0yPjxTUEFOIAogIHN0eWxlPSJGT05ULVNJWkU6 IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj50byB2aXJ0dWFsIG5ldHdv cmtzIAogIHdpdGhpbiBhIHNpbmdsZXRvbiBub2RlPzwvU1BBTj48L0ZPTlQ+PC9QPjwvRk9OVD48 L0RJVj48L0JMT0NLUVVPVEU+CjxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiAKc3R5bGU9IkZPTlQt U0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwiPgo8RElWPkFianVy aW5nIHRoZSBhZGRyZXNzIGFzdW1tYXJpemF0aW9uIHBhcmFkaWdtIGluIGludGVyLWRvbWFpbiBy b3V0aW5nLCB3aHkgCnNob3VsZCBJIHN0aWNrIHRvIGl0IGluIGludHJhLWRvbWFpbiByb3V0aW5n ID86LSggSG93ZXZlciB0aGVyZSwgdGhlIG5lZWQgZm9yIGEgCmZ1bmRhbWVudGFsIGNoYW5nZSBp c24ndCBhcyBpbW1lbnNlLjwvRElWPjwvU1BBTj4KPFA+PC9QPgo8QkxPQ0tRVU9URSAKc3R5bGU9 IlBBRERJTkctTEVGVDogNXB4OyBNQVJHSU4tTEVGVDogNXB4OyBCT1JERVItTEVGVDogYmx1ZSAy cHggc29saWQiPjxGT05UIAogIHN0eWxlPSJCQUNLR1JPVU5ELUNPTE9SOiB0cmFuc3BhcmVudCIg ZmFjZT1BcmlhbCBjb2xvcj0jMDAwMDAwIHNpemU9Mj4KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PEZP TlQgZmFjZT1BcmlhbCBjb2xvcj1ibGFjayBzaXplPTI+PFNQQU4gCiAgc3R5bGU9IkZPTlQtU0la RTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwiPkRvIHRoZSBvdGhlciAK ICBhcHByb2FjaGVzIHByb3ZpZGUgZm9yIGRpc2NvdmVyeSBhbmQgdXRpbGl6YXRpb24gb2YgbXVs dGlwbGU8L1NQQU4+PC9GT05UPjwvUD4KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PEZPTlQgZmFjZT1B cmlhbCBjb2xvcj1ibGFjayBzaXplPTI+PFNQQU4gCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsg Q09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwiPmJvcmRlciAKICByb3V0ZXJzPzwvRk9O VD48L0ZPTlQ+PC9QPjwvQkxPQ0tRVU9URT4KPERJVj4uLi4gYm9yZGVyIHJvdXRlcnMgYXMgdW5k ZXJzdG9vZCBieSBlYWNoIGluZGl2aWR1YWwgYXBwcm9hY2guIEJ1dCB0aGUgCmFuc3dlciBpcyB5 ZXMuPC9ESVY+CjxESVY+Jm5ic3A7PC9ESVY+CjxQIGNsYXNzPU1zb05vcm1hbD48L1NQQU4+Jm5i c3A7PC9QPgo8QkxPQ0tRVU9URSAKc3R5bGU9IlBBRERJTkctTEVGVDogNXB4OyBNQVJHSU4tTEVG VDogNXB4OyBCT1JERVItTEVGVDogYmx1ZSAycHggc29saWQiPjxGT05UIAogIHN0eWxlPSJCQUNL R1JPVU5ELUNPTE9SOiB0cmFuc3BhcmVudCIgZmFjZT1BcmlhbCBjb2xvcj0jMDAwMDAwIHNpemU9 Mj4KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj1ibGFjayBzaXpl PTI+PFNQQU4gCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZB TUlMWTogQXJpYWwiPkRvIHRoZXkgaGF2ZSAKICBmdWxseS1hcnRpY3VsYXRlZCBzcGVjaWZpY2F0 aW9ucyBmb3IgYXV0b21hdGljIEVJRCBhbmQgUkxPQzwvU1BBTj48L0ZPTlQ+PC9QPgogIDxQIGNs YXNzPU1zb05vcm1hbD48Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPWJsYWNrIHNpemU9Mj48U1BBTiAK ICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlh bCI+YWRkcmVzcyAKICBjb25maWd1cmF0aW9uPzwvU1BBTj48L0ZPTlQ+PC9QPjwvRk9OVD48L0JM T0NLUVVPVEU+CjxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiAKc3R5bGU9IkZPTlQtU0laRTogMTBw dDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwiPgo8RElWPlRoZXJlIGlzIG5vIG5l ZWQgZm9yIHN1Y2ggdGhpbmdzLiZuYnNwOyA8L0RJVj48L1NQQU4+CjxQPjwvUD4KPEJMT0NLUVVP VEUgCnN0eWxlPSJQQURESU5HLUxFRlQ6IDVweDsgTUFSR0lOLUxFRlQ6IDVweDsgQk9SREVSLUxF RlQ6IGJsdWUgMnB4IHNvbGlkIj48Rk9OVCAKICBzdHlsZT0iQkFDS0dST1VORC1DT0xPUjogdHJh bnNwYXJlbnQiIGZhY2U9QXJpYWwgY29sb3I9IzAwMDAwMCBzaXplPTI+CiAgPFAgY2xhc3M9TXNv Tm9ybWFsPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9YmxhY2sgc2l6ZT0yPjxTUEFOIAogIHN0eWxl PSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj5EbyB0 aGV5IHN1cHBvcnQgCiAgbXVsdGlob21pbmc/PC9GT05UPjwvRk9OVD48L1A+PC9CTE9DS1FVT1RF Pgo8RElWPldoYXQgYSZuYnNwOyBxdWVzdGlvbiAhIE9mIGNvdXJzZSwgeWVzLjwvRElWPgo8UCBj bGFzcz1Nc29Ob3JtYWw+PC9TUEFOPiZuYnNwOzwvUD4KPEJMT0NLUVVPVEUgCnN0eWxlPSJQQURE SU5HLUxFRlQ6IDVweDsgTUFSR0lOLUxFRlQ6IDVweDsgQk9SREVSLUxFRlQ6IGJsdWUgMnB4IHNv bGlkIj48Rk9OVCAKICBzdHlsZT0iQkFDS0dST1VORC1DT0xPUjogdHJhbnNwYXJlbnQiIGZhY2U9 QXJpYWwgY29sb3I9IzAwMDAwMCBzaXplPTI+CiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxGT05UIGZh Y2U9QXJpYWwgY29sb3I9YmxhY2sgc2l6ZT0yPjxTUEFOIAogIHN0eWxlPSJGT05ULVNJWkU6IDEw cHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj5Qcm92aWRlci1pbmRlcGVuZGVu dCAKICBhZGRyZXNzaW5nPzwvRk9OVD48L0ZPTlQ+PC9QPjwvQkxPQ0tRVU9URT4KPERJVj5QSS0m bmJzcDsgYW5kIFBBLSBpbmRlcGVuZGVudCBhZGRyZXNzaW5nLCBzbyB0byBzcGVhay48L0RJVj4K PFAgY2xhc3M9TXNvTm9ybWFsPjwvU1BBTj4mbmJzcDs8L1A+CjxCTE9DS1FVT1RFIApzdHlsZT0i UEFERElORy1MRUZUOiA1cHg7IE1BUkdJTi1MRUZUOiA1cHg7IEJPUkRFUi1MRUZUOiBibHVlIDJw eCBzb2xpZCI+PEZPTlQgCiAgc3R5bGU9IkJBQ0tHUk9VTkQtQ09MT1I6IHRyYW5zcGFyZW50IiBm YWNlPUFyaWFsIGNvbG9yPSMwMDAwMDAgc2l6ZT0yPgogIDxQIGNsYXNzPU1zb05vcm1hbD48Rk9O VCBmYWNlPUFyaWFsIGNvbG9yPWJsYWNrIHNpemU9Mj48U1BBTiAKICBzdHlsZT0iRk9OVC1TSVpF OiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+SVB2NiAKICBkZXBsb3lt ZW50PzwvRk9OVD48L0ZPTlQ+PC9QPjwvQkxPQ0tRVU9URT4KPERJVj5ZZXMsIGFuZCB3aGF0ZXZl ciBlbHNlLjwvRElWPgo8UCBjbGFzcz1Nc29Ob3JtYWw+PC9TUEFOPiZuYnNwOzwvUD4KPEJMT0NL UVVPVEUgCnN0eWxlPSJQQURESU5HLUxFRlQ6IDVweDsgTUFSR0lOLUxFRlQ6IDVweDsgQk9SREVS LUxFRlQ6IGJsdWUgMnB4IHNvbGlkIj48Rk9OVCAKICBzdHlsZT0iQkFDS0dST1VORC1DT0xPUjog dHJhbnNwYXJlbnQiIGZhY2U9QXJpYWwgY29sb3I9IzAwMDAwMCBzaXplPTI+CiAgPFAgY2xhc3M9 TXNvTm9ybWFsPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9YmxhY2sgc2l6ZT0yPjxTUEFOIAogIHN0 eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj5U cmFmZmljIAogIGVuZ2luZWVyaW5nPzwvRk9OVD48L0ZPTlQ+PC9QPjwvQkxPQ0tRVU9URT4KPERJ Vj5JdCB3b3VsZCZuYnNwO3Byb3ZpZGUgYSBsYXJnZSBtZWFkb3cgZm9yIFRFLCBuZXZlciBldmVy IHNlZW4gYmVmb3JlLjwvRElWPgo8UCBjbGFzcz1Nc29Ob3JtYWw+PC9TUEFOPjxGT05UIHN0eWxl PSJCQUNLR1JPVU5ELUNPTE9SOiB0cmFuc3BhcmVudCIgZmFjZT1BcmlhbCAKY29sb3I9IzAwMDAw MCBzaXplPTI+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj1ibGFjayBzaXplPTI+PFNQQU4gCnN0eWxl PSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj5TZWN1 cmUgCnJlZGlyZWN0aW9uPzwvU1BBTj48L0ZPTlQ+PC9GT05UPjwvUD4KPFAgY2xhc3M9TXNvTm9y bWFsPjxGT05UIHN0eWxlPSJCQUNLR1JPVU5ELUNPTE9SOiB0cmFuc3BhcmVudCIgZmFjZT1Bcmlh bCAKY29sb3I9IzAwMDAwMCBzaXplPTI+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj1ibGFjayBzaXpl PTI+PFNQQU4gCnN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1J TFk6IEFyaWFsIj5wcm9taXNlZC48L1NQQU4+PC9GT05UPjwvUD4KPEJMT0NLUVVPVEUgCnN0eWxl PSJQQURESU5HLUxFRlQ6IDVweDsgTUFSR0lOLUxFRlQ6IDVweDsgQk9SREVSLUxFRlQ6IGJsdWUg MnB4IHNvbGlkIj4KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj1i bGFjayBzaXplPTI+PFNQQU4gCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNr OyBGT05ULUZBTUlMWTogQXJpYWwiPkluZ3Jlc3MgCiAgZmlsdGVyaW5nPzwvU1BBTj48L0ZPTlQ+ PC9QPjwvRk9OVD48L0JMT0NLUVVPVEU+CjxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiAKc3R5bGU9 IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwiPgo8RElW PkdpdmVuIEkga25vdyB0aGUgdG9wb2xvZ3kgYW5kIG5vdCBvbmx5IDMwMCAwMDAgcm91dGVzLCB3 aHkgc2hvdWxkIGluZ3Jlc3MgCmZpbHRlcmluZyBub3QgYmUgcG9zc2libGU/PC9ESVY+CjxESVY+ WWVzLCBpdCBjYW5ub3QgYmUgZG9uZSBhcyBmb2xrcyBhcmUgdXNlZCB0by48L0RJVj48L1NQQU4+ CjxQPjwvUD4KPEJMT0NLUVVPVEUgCnN0eWxlPSJQQURESU5HLUxFRlQ6IDVweDsgTUFSR0lOLUxF RlQ6IDVweDsgQk9SREVSLUxFRlQ6IGJsdWUgMnB4IHNvbGlkIj48Rk9OVCAKICBzdHlsZT0iQkFD S0dST1VORC1DT0xPUjogdHJhbnNwYXJlbnQiIGZhY2U9QXJpYWwgY29sb3I9IzAwMDAwMCBzaXpl PTI+CiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9YmxhY2sgc2l6 ZT0yPjxTUEFOIAogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1G QU1JTFk6IEFyaWFsIj5XaGF0IGFib3V0IAogIG1vYmlsaXR5PzwvRk9OVD48L0ZPTlQ+PC9QPjwv QkxPQ0tRVU9URT4KPERJVj5Zb3UnbGwgYmV0LiBXaXRob3V0IGdlb2dyYXBoaWNhbCBjb29yZGlu YXRlcywmbmJzcDsgbW9iaWxpdHkgd291bGRuJ3QgCmJlLjwvRElWPgo8UCBjbGFzcz1Nc29Ob3Jt YWw+PC9TUEFOPiZuYnNwOzwvUD4KPEJMT0NLUVVPVEUgCnN0eWxlPSJQQURESU5HLUxFRlQ6IDVw eDsgTUFSR0lOLUxFRlQ6IDVweDsgQk9SREVSLUxFRlQ6IGJsdWUgMnB4IHNvbGlkIj48Rk9OVCAK ICBzdHlsZT0iQkFDS0dST1VORC1DT0xPUjogdHJhbnNwYXJlbnQiIGZhY2U9QXJpYWwgY29sb3I9 IzAwMDAwMCBzaXplPTI+CiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxGT05UIGZhY2U9QXJpYWwgY29s b3I9YmxhY2sgc2l6ZT0yPjxTUEFOIAogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBi bGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj5NVFUgaGFuZGxpbmcgZm9yIAogIHR1bm5lbHM/PC9G T05UPjwvRk9OVD48L1A+PC9CTE9DS1FVT1RFPgo8RElWPlllcywgSSB3b3VsZCBhbHNvIG5lZWQg c29tZSBvdXRlciBoZWFkZXIsIGp1c3QgbGlrZSBMSVNQLjwvRElWPgo8RElWPkJ1dCB0aGVyZSBp cyBhbHNvIGFuIGFsdGVybmF0aXZlOiBSZWFsaXphdGlvbiBpbnNpZGUgbGF5ZXIgMi4gVGhpcyB3 b3VsZCAKc2hpZnQgdGhlIHJvdXRpbmcgYXJjaHRpdGVjdHVyZSBmcm9tIElFVEYgdG8gSUVFRS4g VGhpbmsgYWJvdXQgaXQgITwvRElWPgo8UCBjbGFzcz1Nc29Ob3JtYWw+PC9TUEFOPjxGT05UIHN0 eWxlPSJCQUNLR1JPVU5ELUNPTE9SOiB0cmFuc3BhcmVudCIgZmFjZT1BcmlhbCAKY29sb3I9IzAw MDAwMCBzaXplPTI+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj1ibGFjayBzaXplPTI+PFNQQU4gCnN0 eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj5E byB0aGUgb3RoZXIgCmFwcHJvYWNoZXMgaGF2ZSB0aGVpciBiYXNlIG1lY2hhbmlzbXMgd2lkZWx5 IGRlcGxveWVkPC9TUEFOPjwvRk9OVD48L1A+CjxCTE9DS1FVT1RFIApzdHlsZT0iUEFERElORy1M RUZUOiA1cHg7IE1BUkdJTi1MRUZUOiA1cHg7IEJPUkRFUi1MRUZUOiBibHVlIDJweCBzb2xpZCI+ CiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9YmxhY2sgc2l6ZT0y PjxTUEFOIAogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1J TFk6IEFyaWFsIj5pbiBzaGlwcGluZyAKICBpbXBsZW1lbnRhdGlvbnMgZm9yIG1hbnkgeWVhcnMs IGFuZCB3aXRoIG1hbnkgbWlsbGlvbnMgb2Y8L1NQQU4+PC9GT05UPjwvUD4KICA8UCBjbGFzcz1N c29Ob3JtYWw+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj1ibGFjayBzaXplPTI+PFNQQU4gCiAgc3R5 bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwiPnVz ZXJzP188L1NQQU4+PC9GT05UPjwvUD48L0ZPTlQ+PC9CTE9DS1FVT1RFPgo8UCBjbGFzcz1Nc29O b3JtYWw+PFNQQU4gCnN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1G QU1JTFk6IEFyaWFsIj4KPERJVj5XaGF0IGlmIHlvdSBkb24ndCBuZWVkIGh1Z2UgY29yZSByb3V0 ZXJzIGFueW1vcmUgPzwvRElWPjwvU1BBTj4KPFA+PC9QPgo8QkxPQ0tRVU9URSAKc3R5bGU9IlBB RERJTkctTEVGVDogNXB4OyBNQVJHSU4tTEVGVDogNXB4OyBCT1JERVItTEVGVDogYmx1ZSAycHgg c29saWQiPjxGT05UIAogIHN0eWxlPSJCQUNLR1JPVU5ELUNPTE9SOiB0cmFuc3BhcmVudCIgZmFj ZT1BcmlhbCBjb2xvcj0jMDAwMDAwIHNpemU9Mj4KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PEZPTlQg ZmFjZT1BcmlhbCBjb2xvcj1ibGFjayBzaXplPTI+PFNQQU4gCiAgc3R5bGU9IkZPTlQtU0laRTog MTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwiPklzIG1hdHVyaXR5IAogIGlt cG9ydGFudCB0byB0aGlzIGdyb3VwPyBXaGF0IGFib3V0IApjb21wbGV0ZW5lc3M/PC9TUEFOPjwv Rk9OVD48L1A+PC9GT05UPjwvQkxPQ0tRVU9URT4KPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIApz dHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+ CjxESVY+V2hhdCBhYm91dCBnb2luZyBuZXcgcGF0aHMgZm9yIHRoaXMgZ3JvdXAgPzwvRElWPjwv U1BBTj4KPFA+PC9QPgo8QkxPQ0tRVU9URSAKc3R5bGU9IlBBRERJTkctTEVGVDogNXB4OyBNQVJH SU4tTEVGVDogNXB4OyBCT1JERVItTEVGVDogYmx1ZSAycHggc29saWQiPjxGT05UIAogIHN0eWxl PSJCQUNLR1JPVU5ELUNPTE9SOiB0cmFuc3BhcmVudCIgZmFjZT1BcmlhbCBjb2xvcj0jMDAwMDAw IHNpemU9Mj4KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj1ibGFj ayBzaXplPTI+PFNQQU4gCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBG T05ULUZBTUlMWTogQXJpYWwiPkZyZWQ8L1NQQU4+PC9GT05UPjwvUD4KICA8UCBjbGFzcz1Nc29O b3JtYWw+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj1ibGFjayBzaXplPTI+PFNQQU4gCiAgc3R5bGU9 IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwiPmZyZWQu bC50ZW1wbGluQGJvZWluZy5jb20gCiAgPC9TUEFOPjwvRk9OVD48L1A+CiAgPFAgY2xhc3M9TXNv Tm9ybWFsPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9bmF2eSBzaXplPTI+PFNQQU4gCiAgc3R5bGU9 IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IG5hdnk7IEZPTlQtRkFNSUxZOiBBcmlhbCI+PC9TUEFO PjwvRk9OVD4mbmJzcDs8L1A+CiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxGT05UIGZhY2U9QXJpYWwg Y29sb3I9bmF2eSBzaXplPTI+PFNQQU4gCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6 IG5hdnk7IEZPTlQtRkFNSUxZOiBBcmlhbCI+PC9TUEFOPjwvRk9OVD4mbmJzcDs8L1A+CiAgPERJ ViBjbGFzcz1TZWN0aW9uMSAKICBzdHlsZT0iQk9SREVSLVJJR0hUOiBtZWRpdW0gbm9uZTsgUEFE RElORy1SSUdIVDogMGluOyBCT1JERVItVE9QOiBtZWRpdW0gbm9uZTsgUEFERElORy1MRUZUOiA0 cHQ7IFBBRERJTkctQk9UVE9NOiAwaW47IEJPUkRFUi1MRUZUOiBibHVlIDEuNXB0IHNvbGlkOyBQ QURESU5HLVRPUDogMGluOyBCT1JERVItQk9UVE9NOiBtZWRpdW0gbm9uZSI+CiAgPERJVj4KICA8 RElWIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0iVEVYVC1BTElHTjogY2VudGVyIiBhbGlnbj1jZW50 ZXI+PEZPTlQgCiAgZmFjZT0iVGltZXMgTmV3IFJvbWFuIiBzaXplPTM+PFNQQU4gc3R5bGU9IkZP TlQtU0laRTogMTJwdCI+CiAgPEhSIHRhYkluZGV4PS0xIGFsaWduPWNlbnRlciB3aWR0aD0iMTAw JSIgU0laRT0yPgogIDwvU1BBTj48L0ZPTlQ+PC9ESVY+CiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxC PjxGT05UIGZhY2U9VGFob21hIHNpemU9Mj48U1BBTiAKICBzdHlsZT0iRk9OVC1XRUlHSFQ6IGJv bGQ7IEZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IFRhaG9tYSI+RnJvbTo8L1NQQU4+PC9G T05UPjwvQj48Rk9OVCAKICBmYWNlPVRhaG9tYSBzaXplPTI+PFNQQU4gc3R5bGU9IkZPTlQtU0la RTogMTBwdDsgRk9OVC1GQU1JTFk6IFRhaG9tYSI+IAogIEhlaW5lckh1bW1lbEBhb2wuY29tIFtt YWlsdG86SGVpbmVySHVtbWVsQGFvbC5jb21dIDxCUj48Qj48U1BBTiAKICBzdHlsZT0iRk9OVC1X RUlHSFQ6IGJvbGQiPlNlbnQ6PC9TUEFOPjwvQj4gVHVlc2RheSwgTWF5IDE5LCAyMDA5IDEyOjMx IAogIEFNPEJSPjxCPjxTUEFOIHN0eWxlPSJGT05ULVdFSUdIVDogYm9sZCI+VG86PC9TUEFOPjwv Qj4gVGVtcGxpbiwgRnJlZCBMOyAKICBycmdAaXJ0Zi5vcmc8QlI+PEI+PFNQQU4gc3R5bGU9IkZP TlQtV0VJR0hUOiBib2xkIj5TdWJqZWN0OjwvU1BBTj48L0I+IFJlOiAKICBbcnJnXSBSQU5HRVIo Uyk8L1NQQU4+PC9GT05UPjwvUD48L0RJVj4KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PEZPTlQgZmFj ZT0iVGltZXMgTmV3IFJvbWFuIiBzaXplPTM+PFNQQU4gCiAgc3R5bGU9IkZPTlQtU0laRTogMTJw dCI+PC9TUEFOPjwvRk9OVD4mbmJzcDs8L1A+CiAgPERJVj4KICA8RElWPgogIDxQIGNsYXNzPU1z b05vcm1hbD48Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPWJsYWNrIHNpemU9Mj48U1BBTiAKICBzdHls ZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+SW4g ZWluZXIgZU1haWwgdm9tIAogIDE5LjA1LjIwMDkgMDE6MjY6NTcgV2VzdGV1cm9ww6Rpc2NoZSBO b3JtYWx6ZWl0IHNjaHJlaWJ0IAogIEZyZWQuTC5UZW1wbGluQGJvZWluZy5jb206PC9TUEFOPjwv Rk9OVD48L1A+PC9ESVY+CiAgPEJMT0NLUVVPVEUgCiAgc3R5bGU9IkJPUkRFUi1SSUdIVDogbWVk aXVtIG5vbmU7IFBBRERJTkctUklHSFQ6IDBpbjsgQk9SREVSLVRPUDogbWVkaXVtIG5vbmU7IE1B UkdJTi1UT1A6IDVwdDsgUEFERElORy1MRUZUOiA0cHQ7IE1BUkdJTi1CT1RUT006IDVwdDsgUEFE RElORy1CT1RUT006IDBpbjsgTUFSR0lOLUxFRlQ6IDMuNzVwdDsgQk9SREVSLUxFRlQ6IGJsdWUg MS41cHQgc29saWQ7IFBBRERJTkctVE9QOiAwaW47IEJPUkRFUi1CT1RUT006IG1lZGl1bSBub25l Ij4KICAgIDxQIGNsYXNzPU1zb05vcm1hbD48Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPWJsYWNrIHNp emU9Mj48U1BBTiAKICAgIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9O VC1GQU1JTFk6IEFyaWFsIj5idXQgaW4gCiAgICBvdXI8QlI+ZXhwZXJpZW5jZSBSQU5HRVIoUykg aXMgdGhlIG9ubHkgcHJvcG9zYWwgd2l0aCBhIAogICAgY29uc2lzdGVudDxCUj5hcmNoaXRlY3R1 cmFsIGZyYW1ld29yayB0aGF0IGFwcGxpZXMgcmVjdXJzaXZlbHkgaW4gCiAgICBhPEJSPiJuZXR3 b3JrLW9mLW5ldHdvcmtzIiBmYXNoaW9uIGZyb20gdGhlIGdsb2JhbCBJbnRlcm5ldCBjb3JlPEJS PmFsbCB0aGUgCiAgICB3YXkgb3V0d2FyZCB0byBldmVuIHRoZSBzaW1wbGVzdCBvZiBlZGdlIAog IG5ldHdvcmtzLjwvU1BBTj48L0ZPTlQ+PC9QPjwvQkxPQ0tRVU9URT48L0RJVj4KICA8RElWPgog IDxQIGNsYXNzPU1zb05vcm1hbD48Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPWJsYWNrIHNpemU9Mj48 U1BBTiAKICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZ OiBBcmlhbCI+SSBoYXZlIG5ldmVyIAogIHVuZGVyc3Rvb2QgZWl0aGVyIHRoYXQgaW50ZXItIGFu ZCBpbnRyYS1kb21haW4gcm91dGluZyBhcmNoaXRlY3R1cmVzIGhhdmUgdG8gCiAgYmUgc3VjaCBv cnRob2dvbmFsLjwvU1BBTj48L0ZPTlQ+PC9QPjwvRElWPgogIDxESVY+CiAgPFAgY2xhc3M9TXNv Tm9ybWFsPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9YmxhY2sgc2l6ZT0yPjxTUEFOIAogIHN0eWxl PSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj5TbyB3 aGF0ZXZlciBJIAogIHByb3Bvc2VkIG9yIHN1cHBvcnRlZCBzbyBmYXImbmJzcDt3YXMgYWltaW5n IHRvIGEgY29uc2lzdGVudCBhcmNoaXRlY3R1cmFsIAogIGZyYW1ld29yaywgdG9vLjwvU1BBTj48 L0ZPTlQ+PC9QPjwvRElWPgogIDxESVY+CiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxGT05UIGZhY2U9 QXJpYWwgY29sb3I9YmxhY2sgc2l6ZT0yPjxTUEFOIAogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7 IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj5Sb3V0aW5nLCB3aGljaCBpcyAKICBu b3QgYmFzZWQgb24gYWRkcmVzcyBzdW1tYXJpemF0aW9uLCB3b3VsZCBtYWtlIHNlbnNlIGluc2lk ZSBvZiAKICBpbnRyYS1kb21haW4tbmV0d29ya3MgYXMgd2VsbC48L1NQQU4+PC9GT05UPjwvUD48 L0RJVj4KICA8RElWPgogIDxQIGNsYXNzPU1zb05vcm1hbD48Rk9OVCBmYWNlPUFyaWFsIGNvbG9y PWJsYWNrIHNpemU9Mj48U1BBTiAKICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmxh Y2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+PC9TUEFOPjwvRk9OVD4mbmJzcDs8L1A+PC9ESVY+CiAg PERJVj4KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj1ibGFjayBz aXplPTI+PFNQQU4gCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05U LUZBTUlMWTogQXJpYWwiPkhlaW5lcjwvU1BBTj48L0ZPTlQ+PC9QPjwvRElWPjwvRElWPjwvRk9O VD48L0JMT0NLUVVPVEU+CjxESVY+PC9ESVY+CjxESVY+Jm5ic3A7PC9ESVY+PC9GT05UPjwvQk9E WT48L0hUTUw+Cg== -------------------------------1242760907-- From irtf@tonistoev.info Thu May 21 19:54:03 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D5F13A6A6E for ; Thu, 21 May 2009 19:54:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.83 X-Spam-Level: X-Spam-Status: No, score=-0.83 tagged_above=-999 required=5 tests=[AWL=-0.831, BAYES_50=0.001] 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 AkGeWcQ-dRan for ; Thu, 21 May 2009 19:54:02 -0700 (PDT) Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 9C4EF3A68FD for ; Thu, 21 May 2009 19:54:02 -0700 (PDT) Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M7Kv2-0000vi-FW for rrg@irtf.org; Fri, 22 May 2009 05:55:36 +0300 From: Toni Stoev To: IRTF RRG Date: Fri, 22 May 2009 05:55:35 +0300 User-Agent: KMail/1.9.9 References: <200905051235.41286.irtf@tonistoev.info> <4A02C956.50704@gmail.com> In-Reply-To: <4A02C956.50704@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905220555.35681.irtf@tonistoev.info> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi.r1servers.com X-AntiAbuse: Original Domain - irtf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tonistoev.info X-Source: X-Source-Args: X-Source-Dir: Subject: [rrg] Idealism X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2009 02:54:03 -0000 On Thursday 7 May 2009 14:43:18 Scott Brim posted: > Toni Stoev allegedly wrote on 05 05 2009 5:35 AM: > > Intra-domain routing can be considered as a general solution. This > > general solution is the provision of reachability throughout an > > autonomous system. Node locators can be considered intra-domain > > locators. Every locator shall have default association with its > > containing autonomous system in order to be universally recognizable. > > First, see http://tools.ietf.org/html/rfc1955 Scott, I saw that proposal. I have read other network architecture materials too. In my proposals I may be using ideas from other people or I may be thinking up ideas that others have thought up priorly. Either way I'm thinking with my head. What I see so far is that there are many good ideas thought up already. Almost all that we currently need. But what we lack in solutions is idealism. That is, the good ideas to be stretched to their full scale. And solutions to be comprised all of good ideas. Because of the lack of idealism we have global systems pliant to crises. Well, if ideas are too many at once, there won't be any idealistic solution realized. But we need a start. So let us claim idealism. Toni From pfrejborg@gmail.com Fri May 29 06:42:49 2009 Return-Path: X-Original-To: rrg@core3.amsl.com Delivered-To: rrg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F4C73A6987 for ; Fri, 29 May 2009 06:42:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.141 X-Spam-Level: X-Spam-Status: No, score=-2.141 tagged_above=-999 required=5 tests=[AWL=0.458, 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 X9YlWirVUPzE for ; Fri, 29 May 2009 06:42:48 -0700 (PDT) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.248]) by core3.amsl.com (Postfix) with ESMTP id ABFED3A6B1D for ; Fri, 29 May 2009 06:42:48 -0700 (PDT) Received: by an-out-0708.google.com with SMTP id d11so3285199and.37 for ; Fri, 29 May 2009 06:43:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=i6zdzi7IS5JFXDQpqxOKnZN8XFwLPMWG4OhpzZRgQeo=; b=J1JP/AYj47jGsZCBB4wv+M3z2c1m2F8U5unxIXFtijs/1arLmh1YICJY7RK32CrT/2 l9rwpceh337aCiQfF5OIgabNyRmdCPNV7HrLk9FsVOGoC3bVge6zLKuo7h5Q53jhKLff hYGbkt6oC2XEIJoWe0E0HJs+8YBUAk9r7pCuU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=tRZSMtPnIaBFAWvVKiNcWJ0CW4lexvfVmY3eBwAWpf0eB4CcxVpJ0IPi5zv3psXXfc ZGtapeUw6SARlC3HtFN+U+QCGhZX2rKse1Y3rF88kAp91HKdLa1g9f2BGV5h7BI/F15M CiyJiGWMM4Ly9TXCELmwTNkFl4sEWxT6SUNM8= MIME-Version: 1.0 Received: by 10.100.3.13 with SMTP id 13mr3725987anc.75.1243601133054; Fri, 29 May 2009 05:45:33 -0700 (PDT) Date: Fri, 29 May 2009 15:45:33 +0300 Message-ID: <5bc37fd40905290545q2e97e0c6xa2255b5cf3a97aae@mail.gmail.com> From: Patrick Frejborg To: RRG Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [rrg] Updated version of hipv4 framework available X-BeenThere: rrg@irtf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IRTF Routing Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 13:42:49 -0000 Hi, after studying the material from Dagstuhl and the discussion about locator/identifier on the RRG list I realized that I need to update my draft to be in-line with the new definition of locator and identifier. Therefore I changed the syntax in the draft to Area LOCator (ALOC) and Endpoint LOCator (ELOC) to describe a two level hierarchical addressing/routing structure. I also tried to add an identifier to the framework - the reason is that there are some issues that could be improved, but can't be perfectly solved within the network layer. I believe the identifier should be decoupled from the network layer - in order to create a true separation. My conclusion is that a new protocol is needed between the network and transport layer, an "endpoint" or "host" layer is needed. When I was trying to find an identifier solution I stumbled over Host Identity Protocol and it seems that they have been doing an excellent work on an identifier solution. So I'll not describe HIP, instead I mention in my draft where and why HIP could fit in the framework. The hard part is the transition - why should service providers, enterprises and residential users migrate from a solution that is good enough and is still fully functional though it has been announced several times to be in serious trouble?? Offering only technical arguments (address depletion, routing scalability, etc) to the general public will not cause a wave of upgrades. A locator/identifier solution should offer something new - by using non-technical arguments - that could create a movement, a cause that will drive an upgrade. So I have added some "idealism" to my draft. http://tools.ietf.org/html/draft-frejborg-hipv4-02 I hope You can find some thoughts/ideas that can be useful in Your research work. -- patte