[sip-overload] Fwd: I-D Action: draft-ietf-soc-load-control-event-package-06.txt

Charles Shen <charles@cs.columbia.edu> Tue, 01 January 2013 06:05 UTC

Return-Path: <charles.newyork@gmail.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 671B821F85CD for <sip-overload@ietfa.amsl.com>; Mon, 31 Dec 2012 22:05:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AfWeebDWlhBR for <sip-overload@ietfa.amsl.com>; Mon, 31 Dec 2012 22:05:20 -0800 (PST)
Received: from mail-oa0-f42.google.com (mail-oa0-f42.google.com [209.85.219.42]) by ietfa.amsl.com (Postfix) with ESMTP id 94A3021F85B4 for <sip-overload@ietf.org>; Mon, 31 Dec 2012 22:05:20 -0800 (PST)
Received: by mail-oa0-f42.google.com with SMTP id j1so12320403oag.1 for <sip-overload@ietf.org>; Mon, 31 Dec 2012 22:05:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=4+XAgepkyBGvGR2TiuXkABoa+3q1ZXhrMfqfji1W9J0=; b=e+qQWGNeXKmX7MGr97uE5jfLm2dCeKsNi1iDf+0viv9Ozxq+CzXr1hMiUT7Pcwg3qJ kXlBVFy3pI2kWTs4ThtSy8lj155Lxy+k1TMC3psGkmrirIIwJZypx9N9CN0MiL0Tv5dI fbpIwkE24eQ+LswK9vvLZJFeJ0ef6iLRv/9urCn04RTb/q24e0yd/raCH8q2EyYl9ZGT H1vGuBkvyPc+N3eBF89vI9nrCmMexgJo/L+gnWLzKWDpGNgELXAjqxKvm11yxZzhNsxD EeGbBuh3KMGRnU7Zi/MH3/TkbRAZuuZnzZmD1CiOTGzA/ZJyG/pnNvtHxsV8y8DSdFuA YjMQ==
Received: by 10.60.169.177 with SMTP id af17mr23301916oec.103.1357020320081; Mon, 31 Dec 2012 22:05:20 -0800 (PST)
MIME-Version: 1.0
Sender: charles.newyork@gmail.com
Received: by 10.182.12.202 with HTTP; Mon, 31 Dec 2012 22:04:59 -0800 (PST)
In-Reply-To: <20130101055616.28112.34021.idtracker@ietfa.amsl.com>
References: <20130101055616.28112.34021.idtracker@ietfa.amsl.com>
From: Charles Shen <charles@cs.columbia.edu>
Date: Tue, 1 Jan 2013 01:04:59 -0500
X-Google-Sender-Auth: XZpoDT3XzWqqq3aff_TiwW8osMM
Message-ID: <CAPSQ9ZVUuOhFc66YOMriry5gWq4pXspXuaydenQYUvKpi1bCMg@mail.gmail.com>
To: sip-overload@ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: [sip-overload] Fwd: I-D Action: draft-ietf-soc-load-control-event-package-06.txt
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: Tue, 01 Jan 2013 06:05:21 -0000

Dear all, Happy new year!!

And I have produced an updated version based on comments received in
the 2nd WGLC.

1. Terminology: after Shida's several comments on terminology
consistency and possible confusion, I decide to replace "load filter"
with "load filtering policies", so now we are distributing policies
instead of filters. And I consolidated other terms he mentioned, as
well as added a Definitions section.

2. As Vijay suggested, I clarified the meaning of "Notification with
empty body" which is used when a notifier needs to send a notification
but does not have any load filtering policies to convey at the moment.
Since "empty body" may lead to confusion over whether its a body with
empty contents or no body at all, the current wording uses a
"Notification request without a body", but its header needs to
indicate the correct Content-Type as if a body is present (e.g.,
application/load-control+xml) to give the subscriber a sense that the
notifier actually supports what the subscriber is looking for.

3. I put in the sentences proposed by Janet and Keith on handling
message prioritization in Section 6.8

http://www.ietf.org/mail-archive/web/sip-overload/current/msg00861.html

But there is still an openning thread from Bruno on whether we should
replace the SHOULD with MUST in these statements

http://www.ietf.org/mail-archive/web/sip-overload/current/msg00869.html

I will update if needed when finalized.

4. Various technical and editorial improvements based on online and
offline comments and another review.

Thanks!

Charles



---------- Forwarded message ----------
From:  <internet-drafts@ietf.org>
Date: Tue, Jan 1, 2013 at 12:56 AM
Subject: [sip-overload] I-D Action:
draft-ietf-soc-load-control-event-package-06.txt
To: i-d-announce@ietf.org
Cc: sip-overload@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the SIP Overload Control Working Group
of the IETF.

        Title           : A Session Initiation Protocol (SIP) Load
Control Event Package
        Author(s)       : Charles Shen
                          Henning Schulzrinne
                          Arata Koike
        Filename        : draft-ietf-soc-load-control-event-package-06.txt
        Pages           : 40
        Date            : 2012-12-31

Abstract:
   We define a load control event package for the Session Initiation
   Protocol (SIP).  It allows SIP entities to distribute load filtering
   policies to other SIP entities in the network.  The load filtering
   policies contain rules to throttle calls based on their source or
   destination domain, telephone number prefix or for a specific user.
   The mechanism helps to prevent signaling overload and complements
   feedback-based SIP overload control efforts.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-soc-load-control-event-package

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-soc-load-control-event-package-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-soc-load-control-event-package-06


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
sip-overload mailing list
sip-overload@ietf.org
https://www.ietf.org/mailman/listinfo/sip-overload