Service Creation and Extensibility in Iceberg

1
Service Creation and Extensibility in Iceberg

• Bhaskaran Raman
• EECS, U.C.Berkeley
• Iceberg Retreat, Jan 2000

2
Iceberg Goals

• PANS (Potentially Any Network Service)
• Extensibility
• Personal mobility, Service mobility
• Ease of Service Creation
• Scaling, high-availability, fault-tolerance
• Wide-area operation
• Security, authentication, and privacy

3
What do the goals mean?

• Ease of service creation
• Introducing telephony services
• Or, Internet services in Iceberg should be easy
• Involve minimal effort
• Extensibility
• Existing services should be extensible
• To new networks, or device end-points, or service
  end-points

4
Two Exercises

• Exercise 1
• Jukebox service built in Ninja Plays mp3 songs
  from repository
• Making the Ninja Jukebox service available on
  Iceberg end-points
• Exercise 2
• Sanctio service in Ninja Instant-messaging
  system that integrates email, ICQ, and AIM
• Extending the Universal In-box to interface to
  Sanctio end-points as well

5
Ninja Jukebox on Iceberg end-points

• Jukebox developed independently in Ninja
• What does it take to make it accessible through
  Iceberg end-points?
• This is
• Service creation in Iceberg
• Service extension to new end-points
• All it takes is an IAP
• to provide a call setup interface to the Jukebox
  service

6
Ninja Jukebox on Iceberg end-points

• The Jukebox service now becomes available
• to ALL Iceberg end-points
• existing and future
• Why?
• IAP provides network independence
• APC service provides device data-type
  independence
• Naming service provides device name independence

7
Sanctio instant-messages in the Iceberg Universal
In-box

• Sanctio
• Ninja instant messaging service
• Integrates email, ICQ, AIM
• What does it take to include Sanctio messages in
  Universal In-box?
• All it takes is an IAP
• to act as proxy between Sanctio instant messages
  and Iceberg

8
Sanctio instant-messages in the Iceberg Universal
In-box

• The IAP provides an interface for Sanctio
  messages to be delivered to ANY Iceberg end-point
• It uses the Iceberg infrastructure components
• APC service, Naming service, other IAPs
• For reaching out to other Iceberg end-points
• The infrastructure components provide the
  any-to-any capability

9
Other Services?

• What about other kinds of services?
• Telephony services
• Call-back on busy subscriber
• Wildfire like services
• Will the interfaces and components support these?
• What other generic components are needed for
  these other services?