Next Steps in Signaling

Last updated

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 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.

Related Research Articles

In computer network engineering, an Internet Standard is a normative specification of a technology or methodology applicable to the Internet. Internet Standards are created and published by the Internet Engineering Task Force (IETF). They allow interoperation of hardware and software from different sources which allows internets to function. As the Internet became global, Internet Standards became the lingua franca of worldwide communications.

Multiprotocol Label Switching (MPLS) is a routing technique in telecommunications networks that directs data from one node to the next based on labels rather than network addresses. Whereas network addresses identify endpoints the labels identify established paths between endpoints. MPLS can encapsulate packets of various network protocols, hence the multiprotocol component of the name. MPLS supports a range of access technologies, including T1/E1, ATM, Frame Relay, and DSL.

Quality of service (QoS) is the description or measurement of the overall performance of a service, such as a telephony or computer network, or a cloud computing service, particularly the performance seen by the users of the network. To quantitatively measure quality of service, several related aspects of the network service are often considered, such as packet loss, bit rate, throughput, transmission delay, availability, jitter, etc.

In computing, Internet Protocol Security (IPsec) is a secure network protocol suite that authenticates and encrypts packets of data to provide secure encrypted communication between two computers over an Internet Protocol network. It is used in virtual private networks (VPNs).

In computer networking, integrated services or IntServ is an architecture that specifies the elements to guarantee quality of service (QoS) on networks. IntServ can for example be used to allow video and sound to reach the receiver without interruption.

In computing, Internet Key Exchange is the protocol used to set up a security association (SA) in the IPsec protocol suite. IKE builds upon the Oakley protocol and ISAKMP. IKE uses X.509 certificates for authentication ‒ either pre-shared or distributed using DNS ‒ and a Diffie–Hellman key exchange to set up a shared session secret from which cryptographic keys are derived. In addition, a security policy for every peer which will connect must be manually maintained.

A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI) that uses the urn scheme. URNs are globally unique persistent identifiers assigned within defined namespaces so they will be available for a long period of time, even after the resource which they identify ceases to exist or becomes unavailable. URNs cannot be used to directly locate an item and need not be resolvable, as they are simply templates that another parser may use to find an item.

The Resource Reservation Protocol (RSVP) is a transport layer protocol designed to reserve resources across a network using the integrated services model. RSVP operates over an IPv4 or IPv6 and provides receiver-initiated setup of resource reservations for multicast or unicast data flows. It does not transport application data but is similar to a control protocol, like Internet Control Message Protocol (ICMP) or Internet Group Management Protocol (IGMP). RSVP is described in RFC 2205.

<span class="mw-page-title-main">Bob Braden</span> American computer scientist (1934–2018)

Robert Braden was an American computer scientist who played a role in the development of the Internet. His research interests included end-to-end network protocols, especially in the transport and network layers.

Bandwidth management is the process of measuring and controlling the communications on a network link, to avoid filling the link to capacity or overfilling the link, which would result in network congestion and poor performance of the network. Bandwidth is described by bit rate and measured in units of bits per second (bit/s) or bytes per second (B/s).

Resource Reservation Protocol - Traffic Engineering (RSVP-TE) is an extension of the Resource Reservation Protocol (RSVP) for traffic engineering. It supports the reservation of resources across an IP network. Applications running on IP end systems can use RSVP to indicate to other nodes the nature of the packet streams they want to receive. RSVP runs on both IPv4 and IPv6.

Internet Control Message Protocol version 6 (ICMPv6) is the implementation of the Internet Control Message Protocol (ICMP) for Internet Protocol version 6 (IPv6). ICMPv6 is an integral part of IPv6 and performs error reporting and diagnostic functions.

An IPv6 transition mechanism is a technology that facilitates the transitioning of the Internet from the Internet Protocol version 4 (IPv4) infrastructure in use since 1983 to the successor addressing and routing system of Internet Protocol Version 6 (IPv6). As IPv4 and IPv6 networks are not directly interoperable, transition technologies are designed to permit hosts on either network type to communicate with any other host.

<span class="mw-page-title-main">Henning Schulzrinne</span> German-American computer scientist

Henning Schulzrinne is a German-American computer scientist who led research and development of the voice over IP network protocols.

Port Control Protocol (PCP) is a computer networking protocol that allows hosts on IPv4 or IPv6 networks to control how the incoming IPv4 or IPv6 packets are translated and forwarded by an upstream router that performs network address translation (NAT) or packet filtering. By allowing hosts to create explicit port forwarding rules, handling of the network traffic can be easily configured to make hosts placed behind NATs or firewalls reachable from the rest of the Internet, which is a requirement for many applications.

The Session Initiation Protocol (SIP) is the signaling protocol selected by the 3rd Generation Partnership Project (3GPP) to create and control multimedia sessions with multiple participants in the IP Multimedia Subsystem (IMS). It is therefore a key element in the IMS framework.

<span class="mw-page-title-main">Well-known URI</span>

A well-known URI is a Uniform Resource Identifier for URL path prefixes that start with /.well-known/. They are implemented in webservers so that requests to the servers for well-known services or information are available at URLs consistent well-known locations across servers.

References

  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): 133–141. doi:10.1109/MCOM.2005.1522137. S2CID   11652819.
  2. 1 2 3 "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. doi:10.17487/RFC4080 . Retrieved October 12, 2011.
  4. ↑ Henning Schulzrinne, R. Hancock (October 2010). "General Internet Signalling Transport". RFC 5971 . IETF. doi:10.17487/RFC5971 . Retrieved October 12, 2011.
  5. ↑ Manner, J.; Karagiannis, G.; McDonald, A. (2010). "RFC 5974". Tools.ietf.org. doi: 10.17487/RFC5974 . Retrieved 2012-03-18.{{cite journal}}: Cite journal requires |journal= (help)
  6. ↑ Stiemerling, M.; Tschofenig, H.; Aoun, C.; Davies, E. (2008-11-10). "RFC 5973". Tools.ietf.org. doi: 10.17487/RFC5973 . Retrieved 2012-03-18.{{cite journal}}: Cite journal requires |journal= (help)
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.