Re: [RRG] Traffic Engineering scenarios

Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be> Tue, 19 February 2008 19:39 UTC

Envelope-to: rrg-data@psg.com
Delivery-date: Tue, 19 Feb 2008 19:39:27 +0000
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=uclouvain.be; h= message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; q= dns/txt; s=selucl; bh=h0ZKs6DFnMMB3K7iy5y3bhow8II=; b=OSlo7QHuki OoVNIY4Qq8IRfRpBi8LTWvwEGK1bprRoYrlLMH5b6p5kOtmu53dCYoPCusUR6wsl N2eioNI/waEFplio61EF9/BNe79EiNeveYydUb9YoaQczpK2kl8om8gyuY+fBXNK ZUhPfu1OshFClya9hdfLo1ojhovsdTcK8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=uclouvain.be; h=message-id:date:from:reply-to:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=selucl; b= pWmZQRlU41lQ1VcYSQmFQgI1ffVCzDaHaWAZUcwYdN2X159Z/qfjXs7Fo2n7CMCp o/MmroNwzfwZPpqKf9aNILRkMKv05gF9a7SKeClKn8NxJGxtYdrYOsOGky3mkItU 6PNqL0m8zJFyQMCnfLmADzjhvUo6DpYQsJrtJr5Y3s4=
Message-ID: <47BB3056.4080704@uclouvain.be>
Date: Tue, 19 Feb 2008 20:39:02 +0100
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Reply-To: Olivier.Bonaventure@uclouvain.be
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Randall Atkinson <rja@extremenetworks.com>
CC: IRTF Routing RG <rrg@psg.com>
Subject: Re: [RRG] Traffic Engineering scenarios
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit

Randall,

> On occasions when I have talked with IP service providers about
> traffic engineering, I have heard very different inputs from each
> ISP.
> 
> It would be very helpful, I think, for the sundry ISP-aware folks
> here to write up I-Ds on the various TE deployment scenarios
> that they care about, what issues those TE deployments seek
> to solve, and so forth.


Jason Schiller did this exercice some years ago, see :

http://www.nanog.org/mtg-0505/pdf/schiller.pdf

We have used these case studies to develop a new service that would 
allow network operators to influence the paths selected by hosts in a 
shim6 environment, or ITR in a LISP environment. Please find below the 
abstract of the two drafts. The will appear on the IETF mirrors. In the 
meantime, they can be retrieved from http://inl.info.ucl.ac.be/publications

      Title           : The case for an informed path selection service
      Author(s)       : O. Bonaventure, D. Saucez, B. Donnet
      Filename        : draft-bonaventure-informed-path-selection-00.txt

With today's peer-to-peer applications, more and more content is
available from multiple sources.  In tomorrow's Internet hosts will
have multiple paths to reach one destination host with the deployment
of dual-stack IPv4/IPv6 hosts, but also with new techniques such as
shim6 or other locator/identifier mechanisms being discussed within
the IRTF RRG.  All these hosts will need to rank paths in order to
select the best paths to reach a given destination/content.  In this
draft, we propose an informed path selection service that would be
queried by hosts and would rank paths based on policies and
performance metrics defined by the network operator to meet his
traffic engineering objectives.  A companion document describes a
protocol that implements this service.

      Title           : IDIPS : ISP-Driven Informed Path Selection
      Author(s)       : D. Saucez, et al.
      Filename        : draft-saucez-idips-00.txt

This draft describes a simple network-based protocol to facilitate
Path Selection and to improve traffic engineering capabilities in
multihomed corporate networks.  With this protocol, any network
device that requires to select a path among a list of different paths
asks a Traffic Engineering service called IDIPS (ISP-Driven Informed
Path Selection) to obtain an ordered list of the possible paths.  The
ordering is constructed according to policies and performance
requirements of both the host and network provider.


Olivier

-- 
http://inl.info.ucl.ac.be , Universite catholique de Louvain, Belgium

--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg