Home

Simulation

Author's homepage

The Internet of the next generation will see the introduction of Quality of Services (QoS) mechanisms, like Differentiated Services. There is a need for financial regulation mechanisms, i.e. end-to-end pricing of the data transferred, in order to give incentives for not always using the highest QoS.

The Border Pricing Protocol (BPP) is a protocol for the spreading of price information over the Internet. It is inspired by the Border Gateway Protocol (BGP4), the currently Internet standard for inter-Autonomous System routing protocols.

The current version of BPP specifications can be found in my final-year project report on BPP (PDF gziped file).

It also contains a lot of information on BPP, background notes, the development, analysis of the proctocol, simulation results, etc.

A presentation of the protocol I have given at the HPSR and at my university is availaible here.

[ORWe01] Oberle, V., Ritter, H., Wehrle, K.:
"BPP: A Protocol for Exchanging Pricing Information between Autonomous Systems"
Proceedings of HPSR 2001 (IEEE Workshop on High-Performance Switching and Routing), Dallas, USA, 29.-31. Mai 2001

There is a BPP mailing-list to discuss about the development and other issues about BPP.

To subscribe, send mail to Majordomo@telematik.informatik.uni-karlsruhe.de with the following command in the body of your email message:
   subscribe bpp

Jan Gerke originally proposed the idea of the protocol proposed in its CS Final Project at the University of Karlsruhe. It is also presented in a paper by Jan Gerke, Hartmut Ritter, Jochen Schiller, and Klaus Wehrle, also in Karlsruhe.

Vincent Oberlé (vincent at oberle dot org) is the current developer and maintainer of the protocol. He does it in his CS Final Project at the University Pontificia Comillas of Madrid. The project is done in partnership with the Institute of Telematics at University of Karlsruhe in Germany.

Miguel Tejedor, Klaus Wehrle and Hartmut Ritter are the tutors of the project.

If you have any comment to make to the protocol, or even wrote some code, do not hesitate to write me (vincent at oberle dot org).