Network Processing Forum

The Network Processing Forum (NPF) is an industry forum that was organized to facilitate and accelerate the development of next-generation networking and telecommunications products based on network processing technologies. The NPF was merged into the Optical Internetworking Forum in June 2006. The NPF produces Hardware, Software, and Benchmark Interoperability Agreements. These agreements enable equipment manufacturers to lower their time to market and development cost by enabling a robust, multi-vendor ecosystem. It also lowers the total cost of ownership of systems based on their interoperability agreements by enabling investments in test and verification infrastructure as well as enabling competition.

History of the NPF[edit]

The organization was formed to build on the efforts of two former industry groups, the Common Programming Interface Forum (CPIX) and the Common Switch Interface Consortium (CSIX). Chuck Sannipoli then of IBM was the first chairman of the NPF. Misha Nossik then of Solidum Systems, later acquired by Integrated Device Technology was the second chairman of the NPF. Many of the original meetings were held in the Drake Hotel in Chicago, Illinois. The NPF was later absorbed by the Optical Internetworking Forum (OIF) in June 2006.

Organizational form[edit]

The NPF is a member-managed non-profit corporation and operates as a contribution-driven, parliamentary industry forum. Russell Dietz of HiFn is the current chairman and Chuck Sannipoli representing IP Infusion is the vice-chairman. The NPF's board was composed of representatives of Ericsson, HiFn, IBM, Integrated Device Technology, Intel, IP Infusion, and PMC-Sierra.

Hardware interoperability agreements[edit]

The Look-Aside Interface (LA)^[1]^[2] is used by Network Processing Elements (NPE)s to access Network Search Elements, of which CAMs are an example. The Streaming Interface (NPF-SI)^[3] is used by NPEs to talk to each other and to framing devices and to switching devices.

Software interoperability agreements[edit]

Service Application Programming Agreements, (SAPI)s, provide an API to configure or use a service. The following SAPIs have been approved by the NPF:

Interface Management API,^[4] IPSec Service API,^[5] HA Service API, Diffserv Services API,^[6] IPv4 Unicast Forwarding Service API,^[7] IPv6 Unicast Forwarding Service API,^[8] MPLS Forwarding Service API,

Functional APIs, (FAPI)s, are used to configure or use a low level functional block. The following FAPIs have been approved by the NPF:

IPv4 Prefix LPF and FAPI, Generic Classifier LFB and FAPI, Topology Manager FAPI, Messaging LFB,

Benchmarking interoperability agreements[edit]

The NPF has created benchmarks for IP forwarding, IPSEC performance, MPLS forwarding, and switch fabric performance.

Joint projects[edit]

The NPF specified a High Availability framework and service API in conjunction with the Service Availability Forum (SAF). The NPF has also had extensive liaison activity with the Optical Internetworking Forum. In December 2004, the NPF became a founding member of the Mountain View Alliance, a consortium of consortia created to enable Commercial off-the-shelf (COTS) solutions.

External links[edit]

NPF Interoperability Agreements on the OIF site

^ "Archived copy" (PDF). Archived from the original (PDF) on 2008-10-12. Retrieved 2013-09-25.{{cite web}}: CS1 maint: archived copy as title (link)
^ "Archived copy" (PDF). Archived from the original (PDF) on 2013-09-27. Retrieved 2013-09-25.{{cite web}}: CS1 maint: archived copy as title (link)
^ "Archived copy" (PDF). Archived from the original (PDF) on 2008-10-12. Retrieved 2013-09-25.{{cite web}}: CS1 maint: archived copy as title (link)
^ "OIForum". Archived from the original on 2013-09-27. Retrieved 2013-09-25.
^ "Archived copy" (PDF). Archived from the original (PDF) on 2013-09-27. Retrieved 2013-09-25.{{cite web}}: CS1 maint: archived copy as title (link)
^ "Archived copy" (PDF). Archived from the original (PDF) on 2013-09-27. Retrieved 2013-09-25.{{cite web}}: CS1 maint: archived copy as title (link)
^ "Archived copy" (PDF). Archived from the original (PDF) on 2013-09-27. Retrieved 2013-09-25.{{cite web}}: CS1 maint: archived copy as title (link)
^ "Archived copy" (PDF). Archived from the original (PDF) on 2013-09-27. Retrieved 2013-09-25.{{cite web}}: CS1 maint: archived copy as title (link)

[1] "Archived copy" (PDF). Archived from the original (PDF) on 2008-10-12. Retrieved 2013-09-25.{{cite web}}: CS1 maint: archived copy as title (link)

[2] "Archived copy" (PDF). Archived from the original (PDF) on 2013-09-27. Retrieved 2013-09-25.{{cite web}}: CS1 maint: archived copy as title (link)

[3] "Archived copy" (PDF). Archived from the original (PDF) on 2008-10-12. Retrieved 2013-09-25.{{cite web}}: CS1 maint: archived copy as title (link)

[4] "OIForum". Archived from the original on 2013-09-27. Retrieved 2013-09-25.

[5] "Archived copy" (PDF). Archived from the original (PDF) on 2013-09-27. Retrieved 2013-09-25.{{cite web}}: CS1 maint: archived copy as title (link)

[6] "Archived copy" (PDF). Archived from the original (PDF) on 2013-09-27. Retrieved 2013-09-25.{{cite web}}: CS1 maint: archived copy as title (link)

[7] "Archived copy" (PDF). Archived from the original (PDF) on 2013-09-27. Retrieved 2013-09-25.{{cite web}}: CS1 maint: archived copy as title (link)

[8] "Archived copy" (PDF). Archived from the original (PDF) on 2013-09-27. Retrieved 2013-09-25.{{cite web}}: CS1 maint: archived copy as title (link)

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]