GROUP 5
Rich Application Interface (API) for Internet Service
-Specify requirements: Users (or their software agents) specify requirements for a given situation/application
-Willingness to Pay: Users simultaneously indicate how much they will pay for this service

Use Cases (policy & mechanism)
- differentiated bit value
- multiple paths
- service creation

Network
- SLAs
- compliance

Questions:
How much is a user willing to specify (even with agents to make repeat selections)?
Does a richer contracting system suffice (between ISPs)?

Views: 72

Reply to This

Replies to This Discussion

Notes from 30 minute breakout conversation:

Economic viability & Maximize welfare for heterogeneous users.

Define Metrics that applications will need

API should be secure (User to System and System to System)

Open Reporting of information. Auditable

Refine Security as a requirement (should a group look at this?)
Vic,

I hope my Soap Box today will bring your point home ... as my agent language needs a network API for messaging.


Doei ... MXS
Awesome!

Maarten Sierhuis said:
Vic,

I hope my Soap Box today will bring your point home ... as my agent language needs a network API for messaging.


Doei ... MXS
Vic,

I haven't been able to spend more time discussing this with you, but let me offer that I would be more than willing to have my agent language be a "test application" for your approach.


Doei ... MXS

Vic Perotti said:
Awesome!

Maarten Sierhuis said:
Vic,

I hope my Soap Box today will bring your point home ... as my agent language needs a network API for messaging.


Doei ... MXS
MXS-

Superb! I am definitely considering agents at the edge initiating connections. I will take you up on your offer

VP

Reply to Discussion

RSS

© 2017   Created by David Clark.   Powered by

Report an Issue  |  Terms of Service