Next Steps in Signaling (nsis)


In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       Additional NSIS Web Page

Last Modified: 2008-02-14

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

Chair(s):

  • 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@nokia.com>

    Transport Area Advisor:

  • Magnus Westerlund <magnus.westerlund@ericsson.com>

    Secretary(ies):

  • 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
    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 for Proposed Standard
    Feb 2008  Submit 'NSIS QoS Specification Template' to IESG for publication as an Informational RFC
    Feb 2008  Submit 'NSIS QoS Application Protocol' to IESG for publication for Proposed Standard
    Mar 2008  Submit 'NSIS Middle Box Signaling Application Protocol' to IESG for publication for Proposed Standard
    Sep 2008  Submit 'Y.1541 QoS Model' to the IESG for publication as an Informational RFC
    Sep 2008  Submit 'Applicability Statement of NSIS Protocols in Mobile Environments' to the IESG as an Informational RFC
    Sep 2008  Submit 'RMD-QOSM - The Resource Management in Diffserv QOS Model' to the IESG for publication as an Informational RFC
    Nov 2008  Submit 'GIST State Machine' to the IESG for publication as an Informational RFC
    Nov 2008  Submit 'NSIS Operation Over IP Tunnels' to the IESG for publication as an Informational RFC
    Dec 2008  Submit 'NSIS Extensibility Model' to the IESG for publication as an Informational RFC

    Internet-Drafts:

    NSLP for Quality-of-Service Signaling (231095 bytes)
    NAT/Firewall NSIS Signaling Layer Protocol (NSLP) (200237 bytes)
    GIST: General Internet Signalling Transport (377547 bytes)
    QoS NSLP QSPEC Template (144839 bytes)
    Applicability Statement of NSIS Protocols in Mobile Environments (89883 bytes)
    RMD-QOSM - The Resource Management in Diffserv QOS Model (270129 bytes)
    GIST State Machine (47541 bytes)
    Y.1541-QOSM -- Y.1541 QoS Model for Networks Using Y.1541 QoS Classes (37225 bytes)
    NSIS Operation Over IP Tunnels (84811 bytes)
    General Internet Signaling Transport (GIST) over SCTP (22557 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)

    IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

    Return to working group directory.

    Return to IETF home page.