[sip-overload] WGLC: draft-ietf-soc-overload-rate-control - Christer's comments

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 27 June 2013 10:05 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sip-overload@ietfa.amsl.com
Delivered-To: sip-overload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12C9F21F9D2E for <sip-overload@ietfa.amsl.com>; Thu, 27 Jun 2013 03:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.323
X-Spam-Level:
X-Spam-Status: No, score=-4.323 tagged_above=-999 required=5 tests=[AWL=-1.725, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B6dZJx7HrsK7 for <sip-overload@ietfa.amsl.com>; Thu, 27 Jun 2013 03:05:44 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 28D6B21F9CC9 for <sip-overload@ietf.org>; Thu, 27 Jun 2013 03:05:43 -0700 (PDT)
X-AuditID: c1b4fb38-b7fc16d000004a21-da-51cc0e76eaa7
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 91.35.18977.67E0CC15; Thu, 27 Jun 2013 12:05:42 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.6]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.02.0328.009; Thu, 27 Jun 2013 12:05:42 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "sip-overload@ietf.org" <sip-overload@ietf.org>
Thread-Topic: WGLC: draft-ietf-soc-overload-rate-control - Christer's comments
Thread-Index: Ac5zHZr1o6fItvHiQZeBysyYYV71ng==
Date: Thu, 27 Jun 2013 10:05:41 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3BC5DA@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.19]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C3BC5DAESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUyM+JvrW4Z35lAg4NbrC0u7DjGarH/aYID k8eSJT+ZPL5c/swWwBTFZZOSmpNZllqkb5fAldG9oIW14KR3xbJLGg2MTx27GDk4JARMJP5/ 4+hi5AQyxSQu3FvP1sXIxSEkcJRRYveajUwQziJGiZMv1rCBNLAJWEh0/9MGaRARMJY48ngL I4jNLFAp0flwOTuILSzgKXHmyEMmiJoAifV/zzCDtIoI6EnsbTcECbMIqEocun6OBcTmFfCV +LD0OFgrI9AN30+tYYIYKS5x68l8JojbBCSW7DnPDGGLSrx8/I8VwlaUaH/aAHVCvsSTk1/Y IWYKSpyc+YRlAqPwLCSjZiEpm4WkDCKuI7Fg9yc2CFtbYtnC18ww9pkDj5mQxRcwsq9i5ChO LU7KTTcy2MQIjI6DW35b7GC8/NfmEKM0B4uSOO+nU7sChQTSE0tSs1NTC1KL4otKc1KLDzEy cXBKNTDmR4ezeGTuvHRe8F9AX8LMg8vLfSfxp7A5X7ollJF/SnjFieolqv8/TXM8E1Ek9Mvq +X4xt7McRwLn/X+fbCdTzXz01MJrG7uPWS3pUVc82vDugcqRIKuQTjX9j3cmTn9+y5n1xqfL vEtSrx4XPnppt03DNIODT4Xmal6Zl7nNVmGdb9vMFZlrlFiKMxINtZiLihMBC+YfiVwCAAA=
Cc: "draft-ietf-soc-overload-rate-control.all@tools.ietf.org" <draft-ietf-soc-overload-rate-control.all@tools.ietf.org>
Subject: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control - Christer's comments
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-overload>, <mailto:sip-overload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-overload>
List-Post: <mailto:sip-overload@ietf.org>
List-Help: <mailto:sip-overload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-overload>, <mailto:sip-overload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2013 10:05:51 -0000

Hi,

I have read draft-ietf-soc-overload-rate-control-04.txt as part of the WGLC.

I don't have any technical issues, in general I think it's a will written document, and I think the draft can be passed to IESG for publication.

However, there are some editorial issues that you might want to fix at this point, because they might come up sooner or later anyway.

Q1: General: The draft uses "client" and "SIP client" terminology (similar for "server"). I suggest to use consistent terminology.

Q2: General: In some places the draft refers to draft-ietf-soc-overload-control-12 without the "[" and "]" characters around. I assume you have "hardcoded" the draft name, instead of using a reference?

Q3: My understanding is that the Abstract section shall not contain references, so please remove those.

Q4: In Section 3.1, I suggest to replace:


"When in overload, the server uses [draft-ietf-soc-overload-control-

      12] via header oc parameters of SIP responses to inform the clients

      of its overload state and of the target SIP request rate."

...with:


"When in overload, the server uses the Via header field oc parameters [draft-ietf-soc-overload-control-

of SIP responses in order to inform the clients of its overload state and of the target SIP request rate."




Q5: In Section 3.2, I suggest to change the section name from:


"3.2. Summary of via headers parameters for overload control"


...to:



"3.2. Via header field parameters for overload control"



Q6: In Section 3.2, I think it would be good to indicate whether the Via header field parameters are used in SIP Requests, SIP Responses, or both. I know that you describe it later, but I think it would be good to have it already in the overview section.

Q7: In Section 7 you say that there are no IANA considerations. But, don't you need to request IANA to register the new Via header field parameters?

Regards,

Christer