[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: comments on draft-ietf-shim6-proto-03



Shinta,
1.7  Traffic Engineering

  At the time of this writing it is not clear what requirements for
  traffic engineering make sense for the shim6 protocol, since the
  requirements must both result in some useful behavior as well as be
  implementable using a host-to-host locator agility mechanism like
  shim6.  What is clear that whatever they are, shim6 will not be able
  to provide identical capabilities to traffic engineering using BGP
  and Provide Independent IP addresses.


It was not clear to me what the above paragraph means.
Could someone elaborate more on this ?

With shim6, the traffic engineering capabilities will be completely different than with IPv4. With IPv4, ou basically mainly have BGP tweaking today. This is cumbersome and difficult to use efficiently.

With shim6, the selection of the source and destination locators, if done intelligently, can allow : - load balancing between providers (both outgoing and incoming) in an enterprise network
- utilisation of many more paths than with Ipv4
- selection of the path with the lowest delay. By using a coordinate system as in peer-to-peer networks, it is possible to select the best source-destination pair from a delay viewpoint without measuring all possible pairs

You can find a long discussion of traffic engineering capabilities that are allowed by shim6 in Cédric de Launois' PhD thesis :
http://www2.info.ucl.ac.be/people/delaunoi/publications.html

Best regards,


Olivier Bonaventure