[Dime] DOIC: Sections 5.3.1 and 5.3.2
Steve Donovan <srdonovan@usdonovans.com> Mon, 09 December 2013 13:42 UTC
Return-Path: <srdonovan@usdonovans.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 136041AE294 for <dime@ietfa.amsl.com>; Mon, 9 Dec 2013 05:42:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.58
X-Spam-Level: *
X-Spam-Status: No, score=1.58 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dxYztUsZAYkf for <dime@ietfa.amsl.com>; Mon, 9 Dec 2013 05:42:14 -0800 (PST)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [173.247.247.114]) by ietfa.amsl.com (Postfix) with ESMTP id 11FDC1ADF84 for <dime@ietf.org>; Mon, 9 Dec 2013 05:42:14 -0800 (PST)
Received: from cpe-76-187-100-94.tx.res.rr.com ([76.187.100.94]:54113 helo=SDmac.local) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <srdonovan@usdonovans.com>) id 1Vq168-00083A-Qt for dime@ietf.org; Mon, 09 Dec 2013 05:42:09 -0800
Message-ID: <52A5C8B0.2080002@usdonovans.com>
Date: Mon, 09 Dec 2013 07:42:08 -0600
From: Steve Donovan <srdonovan@usdonovans.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "dime@ietf.org" <dime@ietf.org>
Content-Type: multipart/alternative; boundary="------------010805090607030908060607"
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz131.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - usdonovans.com
X-Get-Message-Sender-Via: biz131.inmotionhosting.com: authenticated_id: srdonovan@usdonovans.com
Subject: [Dime] DOIC: Sections 5.3.1 and 5.3.2
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Dec 2013 13:42:15 -0000
The wording in section 5.3.1 and 5.3.2 need to be aligned with the reacting and reporting node concepts. The wording "Request/Response Message Initiator" is misleading in this context. The "initiator" of the message will be either a client or a server. The logic being discussed in 5.3.1 deals with the reacting node and the logic in 5.3.2 deals with the reporting node. Given that an agent can be reacting and/or reporting node but does not initiate the messages, I suggest changing the titles to the sections to: 5.3.1 Reacting Node Endpoint Considerations and 5.3.2 Reporting Node Endpoint Considerations The text in the sections should also be updated to align with the reacting node and reporting node concepts. Regards, Steve
- [Dime] DOIC: Sections 5.3.1 and 5.3.2 Steve Donovan