Evaluation: draft-ietf-sip-sctp - The Stream Control Transmission Protocol as a Transport for for the Session Initiation Protocol

[IESG Secretary <iesg-secretary@ietf.org>]

Last Call to expire on: 2003-07-03

        Please return the full line with your position.

                      Yes  No-Objection  Discuss  Abstain
Harald Alvestrand    [   ]     [   ]     [   ]     [   ]
Steve Bellovin       [   ]     [   ]     [   ]     [   ]
Randy Bush           [   ]     [   ]     [   ]     [   ]
Bill Fenner          [   ]     [   ]     [   ]     [   ]
Ned Freed            [   ]     [   ]     [   ]     [   ]
Ted Hardie           [   ]     [   ]     [   ]     [   ]
Russ Housley         [   ]     [   ]     [   ]     [   ]
Allison Mankin       [ X ]     [   ]     [   ]     [   ]
Thomas Narten        [   ]     [   ]     [   ]     [   ]
Erik Nordmark        [   ]     [   ]     [   ]     [   ]
Jon Peterson         [   ]     [   ]     [   ]     [   ]
Bert Wijnen          [   ]     [   ]     [   ]     [   ]
Alex Zinin           [   ]     [   ]     [   ]     [   ]

2/3 (9) Yes or No-Objection opinions needed to pass.

DISCUSSES AND COMMENTS:
======================



^L 
To: IETF-Announce:; 
Dcc: *******
Cc: RFC Editor <rfc-editor@isi.edu>,
 Internet Architecture Board <iab@iab.org>, sip@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: The Stream Control Transmission Protocol as a 
     Transport for for the Session Initiation Protocol to Proposed Standard 
-------------

The IESG has approved the Internet-Draft 'The Stream Control
Transmission Protocol as a Transport for for the Session Initiation
Protocol' <draft-ietf-sip-sctp-03.txt> as a Proposed Standard. This
document is the product of the Session Initiation Protocol Working
Group. The IESG contact persons are A. Mankin and J. Peterson.

Technical Summary

      The Stream Control Transmission Protocol (SCTP)] has been designed
      as a new transport protocol for the Internet at the
      same layer as TCP and UDP. SCTP has been designed with the transport
      of legacy SS7 signaling messages in mind. A number of
      of the features designed to support transport of such signaling are
      also useful for the transport of SIP (the Session Initiation
      Protocol) [2], which is used to initiate and manage interactive
      sessions on the Internet.

      SIP itself is transport-independent, and can run over any reliable or
      unreliable message or stream transport. However, procedures are only
      defined for transport over UDP and TCP. In order to encourage
      experimentation and evaluation of the appropriateness of SCTP for SIP
      transport, this document defines transport of SIP over SCTP.

      Note that this is not a proposal that SCTP be adopted as the primary
      or preferred transport for SIP; substantial evaluation of SCTP,
      deployment, and experimentation can take place before that happens.
      This specification is targeted at encouraging such experimentation by
      enabling it in SIP.

Working Group Summary

The working group had consensus to advance the draft to Proposed
Standard.

Protocol Quality

An implementation of a SIP client over SCTP in Linux has recently been
announced.

Review of this specification for the IESG was by Allison Mankin.


RFC Editor Note

In the following sentence:
                                                                      This extra layer
      sometimes requires ordered delivery of messages from the transport
      layer (e.g., TLS [6]).

Add a normative reference to RFC 3436 (SCTP over TLS).


Replace Section 6 Security Considerations

    The security issues raised in [2] are not worsened by SCTP, provided the
    advice in Section 4 is followed and SCTP over TLS [cite RFC 2436] is
    used where TLS would be required in [2].