Next Steps in Signaling

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Next Steps in Signaling (NSIS) was an Internet Engineering Task Force working group focusing on the design of a next generation signaling protocol framework and protocol specifications.[1][2]

The NSIS working group was chartered in late 2001 to work on a replacement for Resource Reservation Protocol (RSVP). Chairs included Jukka Manner and Martin Stiemerling.[2] The overall framework of NSIS was presented in 2005.[3] In 2006, the group submitted the first protocol specification for approval by the Internet Engineering Steering Group (IESG). In October 2010, the actual protocol specifications were finally approved and released within the Request for Comments (RFC) series. The work concluded in 2011.[2]

The NSIS protocol suite includes three primary protocols:

  • The General Internet Signalling Transport protocol (GIST)[4]
  • The QoS signaling protocol QoS NSLP [5]
  • The NAT/Firewall signaling protocol NAT/FW NSLP [6]

The QoS NSLP seeks to replace the Resource Reservation Protocol (RSVP) for signaling resource reservations to Internet routers.

The NAT/Firewall NSLP provides a means to talk to network middleboxes, such as firewalls NATs, to punch holes and set up IP address mappings.


  1. ^ X. Fu, Henning Schulzrinne, A. Bader, D. Hogrefe, C. Kappler, G. Karagiannis, H. Tschofenig, S. Van den Bosch (October 2005). "NSIS: a new extensible IP signaling protocol suite". IEEE Communications Magazine. 43 (10). doi:10.1109/MCOM.2005.1522137.{{cite journal}}: CS1 maint: uses authors parameter (link)
  2. ^ a b c "Next Steps in Signaling (nsis)". Charter page. IETF. Archived from the original on April 18, 2011. Retrieved October 12, 2011.
  3. ^ R. Hancock; G. Karagiannis; J. Loughney; S. Van den Bosch (June 2005). "Next Steps in Signaling (NSIS): Framework". RFC 4080. IETF. Retrieved October 12, 2011.
  4. ^ Henning Schulzrinne, R. Hancock (October 2010). "General Internet Signalling Transport". RFC 5971. IETF. Retrieved October 12, 2011.
  5. ^ "RFC 5974". Retrieved 2012-03-18.
  6. ^ "RFC 5973". 2008-11-10. Retrieved 2012-03-18.

External links[edit]