Re: [MEDIACTRL] [sip-overload] WGLC: draft-ietf-soc-overload-design

Volker,

I doubt whether the current draft will serve for all SIP servers. I'm taking the example of B2BUA with media (RTP)topology hiding functionality and there is no DSP, DS0 or DISK resource involved. Here, Server experiences an overload of SIP message not just because of incoming SIP messages but also due to the incoming RTP messages and RTP messages flow varies depend upon the dialog (call) hold time whereas there may not any SIP message when the dialog is established. SIP processor mentioned in the system model of this draft may be shared the physical processor with RTP messages or other protocols messages. We have the problem in incorporating the current SIP overload design in media handling SIP devices.

I'm including mediactrl to hear their experience with SIP overload design and mediactrl combined SIP implementation.

Thanks
Partha

________________________________

From: Volker Hilt [mailto:volker.hilt@alcatel-lucent.com]
Sent: Sun 8/29/2010 11:43 PM
To: Parthasarathi R (partr)
Cc: Salvatore Loreto; sip-overload@ietf.org
Subject: Re: [sip-overload] WGLC: draft-ietf-soc-overload-design

Partha,

the design document discusses problems related to the overload of SIP
messages. Any server that processes SIP messages can experience an
overload of SIP messages. Therefore, the discussions in the draft apply
to all servers that are involved in SIP message processing.

SIP servers that also provide media handling services may need
mechanisms to signal that they are out of trunk lines, DSP processors,
storage capacity for voicmails, etc. These mechanisms will often be
needed at times when the servers can still process SIP messages. These
mechanisms are out of scope for the working group as discussed.

Thanks,

Volker

On 8/29/2010 1:21 PM, Parthasarathi R (partr) wrote:
> Sal/Volker,
> The design document is designed for dedicated SIP signaling servers and
> experiments are done based on the dedicated servers. The same design may
> not scale for SIP server with media handling. As per IETF-78 meeting,
> SIP servers with media handling
> (draft-partha-soc-overload-resource-availability-00,
> draft-jones-sip-overload-sce-00) is outside the scope of this working
> group. I think that it is better to indicate the scope of this overload
> design is for "dedicated SIP servers" only and does not include media
> servers with SIP. Please let me know your opinion on the same.
> Thanks
> Partha
> ------------------------------------------------------------------------
> *From:* sip-overload-bounces@ietf.org on behalf of Salvatore Loreto
> *Sent:* Mon 8/23/2010 4:54 AM
> *To:* sip-overload@ietf.org
> *Cc:* Volker Hilt
> *Subject:* [sip-overload] WGLC: draft-ietf-soc-overload-design
>
> [as chair]
>
> the draft has been update to address all the concerns/suggestions that
> have been raised during
> the F2F meeting in Maastricht:
>
> http://tools.ietf.org/html/draft-ietf-soc-overload-design-01
>
>
> the chairs believe the document has no remaining open issues, and is
> ready for WG last call evaluation.
>
> Today we are starting a two-weeks working group last call.
> This call end on September 5th.
>
> comments and especially full and deep reviews of the draft are really
> appreciate.
>
>
> cheers
> Sal
>
> --
> Salvatore Loreto
> www.sloreto.com
>
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload
>