[sip-overload] rate-control and event-package drafts and normative references

"Vijay K. Gurbani" <vkg@bell-labs.com> Tue, 17 December 2013 13:59 UTC

Return-Path: <vkg@bell-labs.com>
X-Original-To: sip-overload@ietfa.amsl.com
Delivered-To: sip-overload@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 8241E1AE1F5 for <sip-overload@ietfa.amsl.com>; Tue, 17 Dec 2013 05:59:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id SLyMKxZq54Yg for <sip-overload@ietfa.amsl.com>; Tue, 17 Dec 2013 05:59:29 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com []) by ietfa.amsl.com (Postfix) with ESMTP id 115601ADFAB for <sip-overload@ietf.org>; Tue, 17 Dec 2013 05:59:28 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com []) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id rBHDxJo1020535 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 17 Dec 2013 07:59:20 -0600 (CST)
Received: from umail.lucent.com (umail.ndc.lucent.com []) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id rBHDxJJT005496 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 17 Dec 2013 07:59:19 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com []) by umail.lucent.com (8.13.8/TPES) with ESMTP id rBHDxJqH004171; Tue, 17 Dec 2013 07:59:19 -0600 (CST)
Message-ID: <52B058CC.1050508@bell-labs.com>
Date: Tue, 17 Dec 2013 07:59:40 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Charles Shen <charles@cs.columbia.edu>, "NOEL, ERIC C (ERIC C)" <ecnoel@research.att.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on
X-Scanned-By: MIMEDefang 2.64 on
Cc: "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: [sip-overload] rate-control and event-package drafts and normative references
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.15
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, 17 Dec 2013 13:59:30 -0000

Charles, Eric: The Gen-ART review of draft-ietf-soc-overload-control
triggered me to check the references of your drafts, especially whether
the reference to draft-ietf-soc-overload-control is normative or
informative in your drafts.

It appears that both the drafts list draft-ietf-soc-overload-control as
an informative reference.

I believe that this should be changed to a normative reference.

The distinction between normative and informative reference is
captured in http://www.rfc-editor.org/policy.html#policy.refs
 From this reading, it appears reasonable that someone wanting to
implement either rate-control or event-package will need to
read overload-control first.

You can ask the chairs for guidance as well, and assuming that you
do make the change, you can easily do so before IETF last call or
during Auth-48.


- vijay
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq