2.8.6 Next Steps in Signaling (nsis)

NOTE: This charter is a snapshot of the 67th IETF Meeting in San Diego, California USA. It may now be out-of-date.

Last Modified: 2006-10-13


John Loughney <john.loughney@nokia.com>
Martin Stiemerling <stiemerling@netlab.nec.de>

Transport Area Director(s):

Magnus Westerlund <magnus.westerlund@ericsson.com>
Lars Eggert <lars.eggert@netlab.nec.de>

Transport Area Advisor:

Magnus Westerlund <magnus.westerlund@ericsson.com>


Hannes Tschofenig <Hannes.Tschofenig@gmx.net>

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
Mobile IP, Seanoby Context Transfer, etc.  An applicability statement
will be written to discuss the applicability of NSIS protocols in

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 for Proposed Standard
Jun 2006  Submit 'NSIS QoS Specification Template' to IESG for publication as an Informational RFC
Jun 2006  Submit 'NSIS QoS Application Protocol' to IESG for publication for Proposed Standard
Jul 2006  Submit 'NSIS Middle Box Signaling Application Protocol' to IESG for publication for Proposed Standard
Jul 2006  Submit 'Differentiated Service Signaling on the Internet' to the IESG for publication as an Informational RFC
Jul 2006  Submit 'Y.1541 QoS Model' to the IESG for publication as an Informational RFC
Nov 2006  Submit 'Applicability Statement of NSIS Protocols in Mobile Environments' to the IESG as an Informational RFC
Dec 2006  Submit 'General Internet Signaling Transport protocol implementation document' to the IESG for publication as an Informational RFC


  • draft-ietf-nsis-qos-nslp-12.txt
  • draft-ietf-nsis-nslp-natfw-13.txt
  • draft-ietf-nsis-ntlp-11.txt
  • draft-ietf-nsis-qspec-12.txt
  • draft-ietf-nsis-applicability-mobility-signaling-05.txt
  • draft-ietf-nsis-rmd-08.txt
  • draft-ietf-nsis-ntlp-statemachine-02.txt
  • draft-ietf-nsis-y1541-qosm-02.txt
  • draft-ietf-nsis-tunnel-01.txt
  • draft-ietf-nsis-ntlp-sctp-00.txt

    Request For Comments:

    RFC3583 I Requirements of a Quality of Service (QoS)Solution for Mobile IP
    RFC3726 I Requirements for Signaling Protocols
    RFC4080 I Next Steps in Signaling (NSIS): Framework
    RFC4081 I Security Threats for Next Steps in Signaling (NSIS)
    RFC4094 I Analysis of Existing Quality of Service Signaling Protocols
    RFC4230 I RSVP Security Properties

    Meeting Minutes


    QoS NSLP
    Interop Meeting Report
    RMD QoSM
    HyPath QoSM
    Interdomain QoSM