Re: [sip-overload] WG Last Call for draft-ietf-soc-overload-control-12

[<[e-mail]>]

I just have one comment:

Section 5.10.2 says that the response sent by a SIP server to non-participants clients in case of overload is a 503 without the Retry-After header. I did not find any text about the response sent by participating clients when they have to reject a request. I assume they should send a 503 without the Retry-After header as well. I would suggest adding the following sentence at the end of 5.10, after "it will need to reject these requests": In such cases, the SIP client shall reply to the requests with a 503 response without the Retry-After header.

BC


De : [e-mail] [mailto:[e-mail]] De la part de Salvatore Loreto
Envoyé : lundi 11 février 2013 08:35
À : [e-mail]
Cc : Volker Hilt
Objet : Re: [sip-overload] WG Last Call for draft-ietf-soc-overload-control-12

this is just a reminder for this WG Last Call

I haven't seen yet any comment or feedback
please we really need you spend some time to reading and reviewing the draft

thanks a lot
Salvatore

On 2/5/13 3:34 PM, Salvatore Loreto wrote:
Dear WG partecipants,


Volker and I would like to initiate a second 2 weeks WG Last Call on
draft-ietf-soc-overload-control-12 (" Session Initiation Protocol (SIP) Overload Control")
http://tools.ietf.org/id/draft-ietf-soc-overload-control-12.txt

The first WGLC that we run ( http://www.ietf.org/mail-archive/web/sip-overload/current/msg00731.html )
has produced a significant amount of feedback and comments that have been discussed and addressed in subsequent versions

Please send your reviews, as well as expression of support regarding
document readiness for IESG (or not) either to the *soc* mailing list ([e-mail]<mailto:[e-mail]>),
or directly to the WG chairs (Murray Kucherawy and myself).

Comments like "I've read the document and it is Ok to publish" or
"I've read the document and it has the following issues"
are useful and would be gratefully accepted by chairs.


The WG LC will end on Friday, February 19th.


Thank you,
Salvatore as an SoC co-chair.


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.