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

Jouni Korhonen <jouni.nospam@gmail.com> Tue, 13 May 2014 14:30 UTC

Return-Path: <jouni.nospam@gmail.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 636681A00A5 for <dime@ietfa.amsl.com>; Tue, 13 May 2014 07:30:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 eQaV2qKASsOw for <dime@ietfa.amsl.com>; Tue, 13 May 2014 07:30:18 -0700 (PDT)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) by ietfa.amsl.com (Postfix) with ESMTP id E7DBF1A008F for <dime@ietf.org>; Tue, 13 May 2014 07:30:13 -0700 (PDT)
Received: by mail-lb0-f180.google.com with SMTP id p9so342826lbv.11 for <dime@ietf.org>; Tue, 13 May 2014 07:30:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=7mjIJOr6ldXl1UdAKIhQLkZOAdNaLpguU0sforaTK10=; b=i5+bRNv9iwjl5fo7AsjFM1rZTOI9E8s6Az5s41Jb4HuJGggrjXBD9jJFpTzbvViwAn 2BEJFX0V268Kg2nwjaso7QcJuFIS+iMTPKL58/mNGr2gdcoFVslNoJlw3vyfDCKaNeDh vsio2JBh6FNxU3s+RGLvQsep742eJPu5PqRomN+XbvCH5MaLLTl6FTVHjVDrCvxPHOG6 LKz8bilVop6mBdITEiVdvSI7Mn2gxXKdRBeGWn4/euamEvBVdSRyI9Hg3NYxRrGNprc7 xfKYNon3eEGnMXwk0tkXXh596XAHwYt2z0Lj2+PewtmQCCVdrnmbylxnDCCPFlMomj/b BEQQ==
X-Received: by 10.152.29.200 with SMTP id m8mr2076842lah.49.1399991406887; Tue, 13 May 2014 07:30:06 -0700 (PDT)
Received: from [172.16.1.87] (wsip-184-177-183-184.ph.ph.cox.net. [184.177.183.184]) by mx.google.com with ESMTPSA id lc3sm15384316lab.7.2014.05.13.07.30.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 13 May 2014 07:30:06 -0700 (PDT)
Message-ID: <53722C6C.4000405@gmail.com>
Date: Tue, 13 May 2014 17:30:04 +0300
From: Jouni Korhonen <jouni.nospam@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: lionel.morand@orange.com, Benoit Claise <bclaise@cisco.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> <53514D73.3090006@cisco.com> <53714817.8020100@cisco.com> <7656_1399962480_5371BB70_7656_3268_1_6B7134B31289DC4FAF731D844122B36E59FE4D@PEXCVZYM13.corporate.adroot.infra.ftgroup>
In-Reply-To: <7656_1399962480_5371BB70_7656_3268_1_6B7134B31289DC4FAF731D844122B36E59FE4D@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/dCDbQ2IDgonSTnoK5Tgv7j-EJvA
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: Tue, 13 May 2014 14:30:20 -0000

I think the change Lionel made is a good one. Diameter allows us, even 
if not too much recommended, to change M-bits for existing AVP per 
application. Emphasizing the "sanity check" is a good practise imho.

- Jouni

5/13/2014 9:27 AM, lionel.morand@orange.com kirjoitti:
> Hi Benoit,
>
> The "MUST" is maybe not required.
>
> But this will cause interoperability issues if you just say "re-use AVP
> 1" without saying exactly how to set the M-bit. Some may decide to set
> the M-bit as initially defined, others may decide to change it.
>
> So the idea was to provide an absolute recommendation for designers and
> then a MUST/REQUIRED/SHALL for all the AVP flags:
>
> - The M-bit flag MUST be re-evaluated
>
> - Other AVP flags MUST remain unchanged.
>
> If not valid, no problem to revert the change.
>
> Regards,
>
> Lionel
>
> *De :*Benoit Claise [mailto:bclaise@cisco.com]
> *Envoyé :* mardi 13 mai 2014 00:16
> *À :* MORAND Lionel IMT/OLN;
> draft-ietf-dime-app-design-guide.all@tools.ietf.org
> *Cc :* dime mailing list
> *Objet :* Re: [Dime] AD review draft-ietf-dime-app-design-guide
>
> Hi Lionel,
>
> Thanks for the new version 23.
>
> One question regarding the attached picture.
>
>
> What does it mean "MUST be re-evaluated" with a RFC 2119 keyword.
> RFC 2119 keywords are useful for interoperability, and I don't see why
> it's used here.
>
> Regards, Benoit.
>
>     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
>
>
>
>     _______________________________________________
>
>     DiME mailing list
>
>     DiME@ietf.org  <mailto:DiME@ietf.org>
>
>     https://www.ietf.org/mailman/listinfo/dime
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
>
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime
>