1. Programming Interface for IP-based Networks Steve Weinstein & Masa Suzuki {sbw, masa}@ccrl.nj.nec.com C&C Research Labs., NEC USA, Inc. Feb. 13, 1998

2. Presentation Outline Objectives Relevant works Better understanding of the "Programming Interface for Networks" Scope of the Standard Issues

3. Objectives Easy service creation Framework to address new technical challenges New business model for Telecom/Internet software/hardware market

4. Relevant Works Architecture … Integrated Services (RFC1633), Differentiated Services (Internet Draft) Signalling … RSVP (RFC2205, etc.) Open Interface … GSMP (RFC1987) and its extensions (In the context of IP based network)

5. What is an Interface? An interface is an agreed and shared contract, typically static knowledge that is not dynamically modified after the agreement, between at least two parties, supporting an information transfer.

6. What is a Programming Interface for Networks ? A programming interface for Networks is an interface that exposes functionalities to interface users, for manipulation of network resources in various levels, as a foundation that facilitates the introduction of new control and/or management algorithms. (First Crack)

7. Open Interface and "Active Network" Active Network is an interesting topic, but still premature at this moment, especially for standardization. Expose functionalities of NE to outside world Flexibility to modify behavior of NE (Active Signalling, etc. ) Processing Resource Active Device Resource Algorithm Open Interface (IEEE P1520)

8. Reference Model - Routing Table (IP Switch) - Buffers - Service measurement facilities, etc. IP-based Network Resources - Multi party, multi media connection Service, etc. High-level Services - Streams - Customized Data Processing - Customized Billing, etc. Resource Abstractions High-level Services API Abstract Resources API Network Resources API

9. A Programming Interface in the context of IP-based Network (To be investigated) Flow Rate Adjustment Low Rate Hi Rate Flow Rate Adjustment in Multicast Hi(R1) Low(R2)

10. Scope of the Standard Terminology Architectural recommendation Abstract Resources Interface and Network Resources Interface definition with appropriate language

11. What will NOT be included in the Standard? Migration process from existing networks to near future networks with the programming interfaces Performance issues -> supporting activity Implementation issues -> supporting activity

12. Issues that need to be addressed soon Project/Standard Scope, including definition of reference model and terminology Encourage major IP Router/Switch vendors (e.g. CISCO) to join the activity!

13. Summary What is a Programming Interface for Networks? Scope of the standard Urgent Issues * Actual activity will be kicked off in April meeting.