Re: [Dime] Snapshot of -02 version of DOIC draft

Steve Donovan <srdonovan@usdonovans.com> Mon, 17 March 2014 17:12 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 B84801A044A for <dime@ietfa.amsl.com>; Mon, 17 Mar 2014 10:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.28
X-Spam-Level:
X-Spam-Status: No, score=0.28 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 uxLQiY1rK6Sz for <dime@ietfa.amsl.com>; Mon, 17 Mar 2014 10:12:05 -0700 (PDT)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [173.247.247.114]) by ietfa.amsl.com (Postfix) with ESMTP id C627E1A0448 for <dime@ietf.org>; Mon, 17 Mar 2014 10:12:05 -0700 (PDT)
Received: from [137.254.4.59] (port=8659 helo=SDmac.local) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <srdonovan@usdonovans.com>) id 1WPb4s-0002GL-5h; Mon, 17 Mar 2014 10:11:57 -0700
Message-ID: <53272CD9.9080904@usdonovans.com>
Date: Mon, 17 Mar 2014 12:11:53 -0500
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: Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com>, "dime@ietf.org" <dime@ietf.org>
References: <531AFCA4.1010408@usdonovans.com> <087A34937E64E74E848732CFF8354B920978BCDA@ESESSMB101.ericsson.se>
In-Reply-To: <087A34937E64E74E848732CFF8354B920978BCDA@ESESSMB101.ericsson.se>
Content-Type: multipart/alternative; boundary="------------030901060906090105010607"
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
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/GMPRZpLUIUbVUeN_l30muayoLpI
Subject: Re: [Dime] Snapshot of -02 version of DOIC draft
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, 17 Mar 2014 17:12:08 -0000

Maria Cruz,

I updated the text based on what was put in the issue tracker when you
closed the issue.

Are you suggesting that this issue needs to be re-opened so we can
discuss whether OC-Supported-Features is needed in mid-session requests?

Steve

On 3/11/14 7:06 AM, Maria Cruz Bartolome wrote:
>
> Hello Steve,
>
>  
>
> According to conclusion on #Issue 51: OC-Supported-Feature AVP MUST be
> included in all request messages sent by a DOIC supporting node. (not
> yet agreed).
>
>  
>
> Text marked in green below requires updates:
>
>  
>
> 5.3.1.  Reacting Node Endpoint Considerations
>
>  
>
>    The basic principle is that the request message initiating endpoint
>
>    (i.e. the "reacting node") announces its support for the overload
>
>    control mechanism by including in the request message the OC-
>
>    Supported-Features AVP with those capabilities it supports and is
>
>    willing to use for this Diameter session (or transaction in a case of
>
>    a non-session state maintaining applications, see Section 3.1.2 for
>
>    more details on Diameter sessions).  It is RECOMMENDED that the
>
>    request message initiating endpoint includes the capability
>
>    announcement into every request regardless it has had prior message
>
>    exchanges with the give remote endpoint.  In a case of a Diameter
>
>    session maintaining application, sending the OC-Supported-Features
>
>    AVP in every message is not really necessary after the initial
>
>    capability announcement or until there is a change in supported
>
>    features.
>
>  
>
>    Once the endpoint that initiated the request message receives an
>
>    answer message from the remote endpoint, it can detect from the
>
>    received answer message whether the remote endpoint supports the
>
>    overload control solution and in a case it does, what features are
>
>    supported.  The support for the overload control solution is based on
>
>    the presence of the OC-Supported-Features AVP in the Diameter answer
>
>    for existing application.
>
>  
>
>  
>
> Best regards
>
> /MCruz
>
>  
>
> *From:*DiME [mailto:dime-bounces@ietf.org] *On Behalf Of *Steve Donovan
> *Sent:* sábado, 08 de marzo de 2014 12:19
> *To:* dime@ietf.org
> *Subject:* [Dime] Snapshot of -02 version of DOIC draft
>
>  
>
> All,
>
> I have made updates to the -02 version of the DOIC draft based on
> resolution to the following issues:
>
> 24, 32, 50, 51, 52, 47 and 37
>
> I had also started to make updates for issues 29, 31 and 34 before we
> agreed that the proposed text needs to be updated in the issue tracker
> before the edits are made.  I'll clean up these updates when we have
> the wording put into issue tracker.
>
> To those who own issues in issue tracker, if we have resolution of the
> issue on the mailing list please update issue tracker ASAP so the
> edits can be put into the -02 draft.
>
> Thanks,
>
> Steve
>