Re: [Dime] AD review draft-ietf-dime-app-design-guide

Benoit Claise <bclaise@cisco.com> Fri, 18 April 2014 16:06 UTC

Return-Path: <bclaise@cisco.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 665381A0455 for <dime@ietfa.amsl.com>; Fri, 18 Apr 2014 09:06:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.772
X-Spam-Level:
X-Spam-Status: No, score=-9.772 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 7zJyLXY-AmU9 for <dime@ietfa.amsl.com>; Fri, 18 Apr 2014 09:06:21 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 0F0531A0451 for <dime@ietf.org>; Fri, 18 Apr 2014 09:06:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12329; q=dns/txt; s=iport; t=1397837172; x=1399046772; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=RIjQPDaENH/moLbDdimM53Lord/1DtVidH9u4MfKozY=; b=Rj0BZMpwM8Pl/YBfAX1egNWlIf5/sjbz60f0Kb4u5x0KrsL51W7atS2w IN/7D1Leb7jnDWZAYad6Xf2Z9RCeKnIsuyYnLE87Cd/Wwqwo/shkU1Xpc lNQ5DhTsb7hhZAOz01DLoagCKYeC0hcT7RZz3+i3TXfJMD2eidpU5Zfjw 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AroEALtMUVOtJssW/2dsb2JhbABagkKKWbsFgTN0giYBAQQtSwEQCyEWDwkDAgECAUUGAQwBBwEBEIgtzR8XjXULEQFQB4Q4AQOYboZYi3eDMzuBNQ
X-IronPort-AV: E=Sophos; i="4.97,884,1389744000"; d="scan'208,217"; a="19137948"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 18 Apr 2014 16:06:11 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s3IG6BhY017688; Fri, 18 Apr 2014 16:06:11 GMT
Message-ID: <53514D73.3090006@cisco.com>
Date: Fri, 18 Apr 2014 18:06:11 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: lionel.morand@orange.com, "draft-ietf-dime-app-design-guide.all@tools.ietf.org" <draft-ietf-dime-app-design-guide@tools.ietf.org>
References: <52D9030B.3010402@cisco.com> <533BD276.7000401@cisco.com> <22885_1396976646_53442C06_22885_3037_1_6B7134B31289DC4FAF731D844122B36E54D5C4@PEXCVZYM13.corporate.adroot.infra.ftgroup>
In-Reply-To: <22885_1396976646_53442C06_22885_3037_1_6B7134B31289DC4FAF731D844122B36E54D5C4@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Content-Type: multipart/alternative; boundary="------------020205050006050807080003"
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/b3hkVoAXx6WZGz-fvq37rg7uf2o
Cc: dime mailing list <dime@ietf.org>
Subject: Re: [Dime] AD review draft-ietf-dime-app-design-guide
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: Fri, 18 Apr 2014 16:06:23 -0000

Hi Lionel,

Thanks for the new version.
See in line
>
>
>
> - When I read the document, it looked to me as a BCP.
>
> BCP definition from RFC 2026:
>
>     5.  BEST CURRENT PRACTICE (BCP) RFCs
>
>       
>
>         The BCP subseries of the RFC series is designed to be a way to
>
>         standardize practices and the results of community deliberations.
>
> Interestingly, the charter mentions:
>
> May 2012, Submit 'Diameter Application Design Guidelines' to the IESG 
> for consideration as a BCP document
>
> */[LM] discussed in another email thread./*
>
>
> If you go to BCP, don't forget to update the abstract, and the writeup.
>
Abstract:

    It is meant as a guidelines document and
    therefore as informative in nature.

I would remove this sentence. Informative and BCP don't go along very well.

Jouni, don't forget to update the writeup.

>
> *//*
>
> *//**//**//*
>
>
> - Editorial in section 5.7
> OLD:
>
> Destination- Realm
>   
> NEW:
> Destination-Realm
> */
> /*
Still there.
>
>
> *//**//*
>
>
>
> - Section 5.9
>
>   Applications that do not understand these AVPs can discard
>     them upon receipt.
>
> Generic comment: Each time there is a sentence like this one above, we 
> should mention RFC 6733 as the reference.
> This document is not an extension/deviation to RFC 6733.
>
> */[LM] ok/*
>
Still there.
>
> *//*
>
> *//*

Regards, Benoit