IETF Logo Mail Archive

Re: [Dime] Issue#29 proposed conclusion

Steve Donovan <srdonovan@usdonovans.com> Fri, 21 March 2014 13:20 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 027B31A096E for <dime@ietfa.amsl.com>; Fri, 21 Mar 2014 06:20:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level:
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 JOR8WIlYkftf for <dime@ietfa.amsl.com>; Fri, 21 Mar 2014 06:20:01 -0700 (PDT)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [23.235.209.16]) by ietfa.amsl.com (Postfix) with ESMTP id 077E11A03E2 for <dime@ietf.org>; Fri, 21 Mar 2014 06:20:01 -0700 (PDT)
Received: from cpe-76-187-100-94.tx.res.rr.com ([76.187.100.94]:51392 helo=SDmac.local) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <srdonovan@usdonovans.com>) id 1WQzMU-0000JV-CO for dime@ietf.org; Fri, 21 Mar 2014 06:19:51 -0700
Message-ID: <532C3C76.4050200@usdonovans.com>
Date: Fri, 21 Mar 2014 08:19:50 -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.4.0
MIME-Version: 1.0
To: dime@ietf.org
References: <5BCBA1FC2B7F0B4C9D935572D9000668151B3B73@DEMUMBX014.nsn-intra.net> <32C8E469-48AE-4336-AF92-F6EB2B12EDA4@nostrum.com> <530BA310.4090100@usdonovans.com> <8BE5229D-E276-4084-B6EB-DBF89817E02F@nostrum.com> <5327372B.1040600@usdonovans.com>
In-Reply-To: <5327372B.1040600@usdonovans.com>
Content-Type: multipart/alternative; boundary="------------030400090506030305070003"
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/6L8m-8RbTZD_J6s8HhUarO6foO0
Subject: Re: [Dime] Issue#29 proposed conclusion
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, 21 Mar 2014 13:20:03 -0000

Having seen no additional discussion on this I will close the issue with
the suggested text.

Regards,

Steve

On 3/17/14 12:55 PM, Steve Donovan wrote:
> All,
>
> I believe we have consensus on this ticket.
>
> I had put the following into my issue status document:
>
> Agreed -- Removed OC-Sequence-Number from OC-Supported-Features AVP.
>
> Agreed -- The scope of an OC-Supported-Features AVP is a single
> transaction.
>
> Agreed -- Diameter nodes that support DOIC must include the
> OC-Supported-Features AVP in all requests.
>
>
> I believe that this translates into the text changes outlined below. 
> If we have agreement on the text below we can close the issue and I'll
> update the text in the -02 draft accordingly.
>
> Regards,
>
> Steve
>
> -----
>
> Section 4.1:
>
> Remove < OC-Sequence-Number >  from OC-Supported-Features syntax
> description.
>
> Remove paragraph 3 that starts "OC-Sequence-Number AVP is used..."
>
> Section 4.4, Paragraph 1:
>
> Remove reference to section 4.1.
>
> Section 5.3.1, Paragraph 1:
>
> Change:
>
> 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. To: The lifetime of a capability announcement is limited
> to a single transaction. As a result, the reacting node MUST include
> the capability announcement in all request messages.
>
>
>
>
>
>
>
>
> On 2/24/14 5:02 PM, Ben Campbell wrote:
>> On Feb 24, 2014, at 1:52 PM, Steve Donovan <srdonovan@usdonovans.com> wrote:
>>
>>> I agree.
>>>
>>> I also think that we agreed that the lifetime of the OC-Supported-Features AVP is a single transaction and that the OC-Supported-Features AVP must be included in all requests originated by a Diameter node supporting DOIC.
>> +1, and my previous agreement was based on that assumption.
>>
>>
>>> Steve
>>>
>>> On 2/20/14 4:31 PM, Ben Campbell wrote:
>>>> I concur with removing the sequence number from OC-Supported-Features.
>>>>
>>>>
>
>
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime

v2.23.0 | Report a Bug | By Email