Internet Engineering Task Force

Next Steps in Signaling (nsis)

Last Modified: 2010-05-25

Additional information is available at tools.ietf.org/wg/nsis

Chair(s):

Transport Area Director(s):

Transport Area Advisor:

Lars Eggert <lars.eggert@nokia.com>

Mailing Lists:

General Discussion: nsis@ietf.org
To Subscribe: nsis-request@ietf.org
In Body: (un)subscribe
Archive: http://www.ietf.org/mail-archive/web/nsis/index.html

Description of Working Group:

The Next Steps in Signaling Working Group is responsible for
standardizing an IP signaling protocol with QoS signaling as the first
use case. This working group will concentrate on a two-layer
signaling paradigm. The intention is to re-use, where appropriate,
the protocol mechanisms of RSVP, while at the same time simplifying it
and applying a more general signaling model.

The existing work on the requirements, the framework and analysis of
existing protocols will be completed and used as input for the
protocol work.

NSIS will develop a transport layer signaling protocol for the
transport of upper layer signaling. In order to support a toolbox or
building block approach, the two-layer model will be used to separate
the transport of the signaling from the application signaling. This
allows for a more general signaling protocol to be developed to
support signaling for different services or resources, such as NAT &
firewall traversal and QoS resources. The initial NSIS application
will be an optimized RSVP QoS signaling protocol. The second
application will be a middle box traversal protocol. An informational
document detailing how Differentiated Services can be signaled
with the QoS Signaling protocol will be made.

Security is a very important concern for NSIS. The working group will
study and analyze the threats and security requirements for
signaling. Compatibility with authentication and authorization
mechanisms such as those of Diameter, COPS for RSVP (RFC 2749) and
RSVP Session Authorization (RFC 3250), will be addressed.

It is a non-goal of the working group to develop new resource
allocation protocols. Traffic engineering is out of scope of this
WG. Additionally, third party signaling is out of scope of this WG.
New mobility and AAA protocols are out of scope of the WG.
However, the work produced in this Working Group should work with
existing IETF mobility and AAA protocols, including (but not limited
to)
Mobile IP, Seanoby Context Transfer, etc. An applicability statement
will be written to discuss the applicability of NSIS protocols in
mobile
environments.

NSIS also welcomes participation and expression of requirements
requirements from non-IETF standards organization members, for
instance 3GPP, 3GPP2 and ITU-T.

Goals and Milestones:

Done		Submit 'Signaling Requirements' to IESG for publication as an Informational RFC.
Done		Submit 'Next Steps in Signaling: Framework' to IESG for publication as Informational RFC
Done		Submit 'Analysis of Existing Signaling Protocols' to IESG as Informational RFC
Done		Submit 'RSVP Security Properties' to IESG as Informational RFC
Done		Submit 'NSIS Threats' to IESG as Informational RFC
Done		Submit 'NSIS Transport Protocol' to IESG for publication as Experimental RFC
Done		Submit 'NSIS QoS Specification Template' to IESG for publication as an Informational RFC
Done		Submit 'NSIS QoS Application Protocol' to IESG for publication as Experimental RFC
Done		Submit 'NSIS Middle Box Signaling Application Protocol' to IESG for publication as Experimental RFC
Done		Submit 'Y.1541 QoS Model' to the IESG for publication as an Informational RFC
Done		Submit 'Applicability Statement of NSIS Protocols in Mobile Environments' to the IESG as an Informational RFC
Done		Submit 'RMD-QOSM - The Resource Management in Diffserv QOS Model' to the IESG for publication as an Informational RFC
Done		Submit 'GIST State Machine' to the IESG for publication as an Informational RFC
Done		Submit 'NSIS Extensibility Model' to the IESG for publication as an Informational RFC
Done		Submit 'SCTP transport for GIST' to the IESG for publication as an Experimental RFC
May 2010		Submit 'NSIS Operation Over IP Tunnels' to the IESG for publication as an Informational RFC

Internet-Drafts:

NSIS Protocols operation in Mobile Environments (96265 bytes)
NSIS Operation Over IP Tunnels (70212 bytes)
General Internet Signaling Transport (GIST) over Stream Control Transmission Protocol (SCTP) and Datagram Transport Layer Security (DTLS) (27434 bytes)
Authorization for NSIS Signaling Layer Protocols (87787 bytes)

Request For Comments:

Requirements of a Quality of Service (QoS)Solution for Mobile IP (RFC 3583) (22541 bytes)
Requirements for Signaling Protocols (RFC 3726) (98020 bytes)
Analysis of Existing Quality of Service Signaling Protocols (RFC 4094) (103146 bytes)
Next Steps in Signaling (NSIS): Framework (RFC 4080) (122470 bytes)
Security Threats for Next Steps in Signaling (NSIS) (RFC 4081) (67786 bytes)
RSVP Security Properties (RFC 4230) (121030 bytes)
Using and Extending the NSIS Protocol Family (RFC 5978) (0 bytes)
Y.1541-QOSM -- Model for Networks Using Y.1541 QoS Classes (RFC 5976) (0 bytes)
QSPEC Template for the Quality-of-Service NSIS Signaling Layer Protocol (NSLP) (RFC 5975) (0 bytes)
NSIS Signaling Layer Protocol (NSLP) for Quality-of-Service Signaling (RFC 5974) (0 bytes)
NAT/Firewall NSIS Signaling Layer Protocol (NSLP) (RFC 5973) (0 bytes)
General Internet Signaling Transport (GIST) State Machine (RFC 5972) (0 bytes)
GIST: General Internet Signalling Transport (RFC 5971) (0 bytes)
RMD-QOSM: The NSIS Quality-of-Service Model for Resource Management in Diffserv (RFC 5977) (0 bytes)