IETF Logo Mail Archive

Re: [Dime] [dime] #41: Need better overview

Steve Donovan <srdonovan@usdonovans.com> Mon, 10 February 2014 16:37 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 908C01A07EE for <dime@ietfa.amsl.com>; Mon, 10 Feb 2014 08:37:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 BqD7jX6R9nn2 for <dime@ietfa.amsl.com>; Mon, 10 Feb 2014 08:37:28 -0800 (PST)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [66.117.0.129]) by ietfa.amsl.com (Postfix) with ESMTP id E77DB1A0882 for <dime@ietf.org>; Mon, 10 Feb 2014 08:37:28 -0800 (PST)
Received: from cpe-76-187-100-94.tx.res.rr.com ([76.187.100.94]:57624 helo=SDmac.local) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <srdonovan@usdonovans.com>) id 1WCtq9-0003DA-T4; Mon, 10 Feb 2014 08:36:17 -0800
Message-ID: <52F90040.6020909@usdonovans.com>
Date: Mon, 10 Feb 2014 10:37:20 -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.3.0
MIME-Version: 1.0
To: lionel.morand@orange.com, "dime@ietf.org" <dime@ietf.org>, "draft-docdt-dime-ovli@tools.ietf.org" <draft-docdt-dime-ovli@tools.ietf.org>, "ben@nostrum.com" <ben@nostrum.com>
References: <057.4fed1570cbb27d114428d8cc6fe5dcd2@trac.tools.ietf.org> <8933_1391878974_52F6633D_8933_14099_1_6B7134B31289DC4FAF731D844122B36E49395B@PEXCVZYM13.corporate.adroot.infra.ftgroup>
In-Reply-To: <8933_1391878974_52F6633D_8933_14099_1_6B7134B31289DC4FAF731D844122B36E49395B@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Content-Type: multipart/alternative; boundary="------------040501080404040709090903"
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: Re: [Dime] [dime] #41: Need better overview
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, 10 Feb 2014 16:37:30 -0000

I think the way to handle this issue in the issue tracker is to assign
it to one of the authors and that author would then be responsible for
generating overview text.

Steve

On 2/8/14 11:02 AM, lionel.morand@orange.com wrote:
> Hi Ben,
>
> Any proposal?
>
> Regards,
>
> Lionel
>
> -----Message d'origine-----
> De : DiME [mailto:dime-bounces@ietf.org] De la part de dime issue tracker
> Envoyé : vendredi 7 février 2014 21:55
> À : draft-docdt-dime-ovli@tools.ietf.org; ben@nostrum.com
> Cc : dime@ietf.org
> Objet : [Dime] [dime] #41: Need better overview
>
> #41: Need better overview
>
>  The overview is short on explanation. We need a high level, non-normative
>  "how it works" description of the mechanism, including roles,
>  responsibilities, associations, and information flows. This doesn't need
>  too much detail (e.g. message and AVP definitions belong elsewhere.)
>
>  Some of the information in the endpoint architecture section would be
>  better off here.
>

v2.23.0 | Report a Bug | By Email