IETF Logo Mail Archive

Re: [Dime] DOIC #49

Jouni Korhonen <jouni.nospam@gmail.com> Fri, 18 July 2014 15:11 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 A109C1ABB18 for <dime@ietfa.amsl.com>; Fri, 18 Jul 2014 08:11:53 -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 7o_A9e4_BJGz for <dime@ietfa.amsl.com>; Fri, 18 Jul 2014 08:11:49 -0700 (PDT)
Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09A3A1ABB2C for <dime@ietf.org>; Fri, 18 Jul 2014 08:11:46 -0700 (PDT)
Received: by mail-pa0-f49.google.com with SMTP id hz1so5519305pad.8 for <dime@ietf.org>; Fri, 18 Jul 2014 08:11:45 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ZZygNtdu9PYJxz01dXXETuc+wc0Hb0uzOgKOwR7bg9I=; b=BnsMJbA6K+wFuWa/XGEeMWgu/45ENYsqU0k2gQ1sSPNHClLotiwkaUrYaGQVkt/6sn 53M5TN3wCf6y2/sok8AthrePDvhC6FUHM2PRXTCPankzTzSFzaBLPkK6GjghHWSmmjU/ EcsE0QqhwJoOkshBVHwzuVzmjSnWX06j5DQBPLjl329L1OSOHAnnTg8V8UK5OTOyKt56 ZTQ6gODTXxDtwk0iNFXDHMZjAN+EhWB8k3mAQL1RL5OF/7Y3ceKqWXutZnMUG35t9Q9t xyWOv0Ovvql2vJ/DBPAgXE2AKWkb/7ki9CxkP8smbN99hi5A8KlaayHDKsQUrgnpGPU4 h6Dg==
X-Received: by 10.68.227.4 with SMTP id rw4mr5962705pbc.3.1405696305458; Fri, 18 Jul 2014 08:11:45 -0700 (PDT)
Received: from [10.199.9.133] ([63.133.197.135]) by mx.google.com with ESMTPSA id by1sm5863868pbb.75.2014.07.18.08.11.43 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Jul 2014 08:11:44 -0700 (PDT)
Message-ID: <53C93928.9070406@gmail.com>
Date: Fri, 18 Jul 2014 18:11:36 +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.6.0
MIME-Version: 1.0
To: Steve Donovan <srdonovan@usdonovans.com>, "dime@ietf.org" <dime@ietf.org>
References: <53C8F215.9040803@usdonovans.com>
In-Reply-To: <53C8F215.9040803@usdonovans.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/U5q3l5aotWnKUp-D2X6mCBZzU_g
Subject: Re: [Dime] DOIC #49
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 Jul 2014 15:11:53 -0000

We should close this as fixed.

- Jouni

7/18/2014 1:08 PM, Steve Donovan kirjoitti:
> I propose that we can close issue #49 based on existing text.
>
> Here's the wording from issue #49:
>
> ----
>
> The capabilities announcement mechanism needs serious rethought.
> Specifically, the lifetime of the state associated with a capabilities
> announcement is unclear. It does not make sense to tie that lifetime to
> Diameter session lifetimes, unless we expect to have different
> capability sets for different sessions. (and it doesn't help at all for
> non-session applications or pseudo-sessions.)
>
> I think we either need to mandate that the capabilities are stateless,
> that is, must be included in every request, and any OLR in a response
> must match the OC-Supported-Features from the corresponding request.
> Otherwise, we need a way to activate and deactivate the set associated
> with a capabilities set.
>
> (This is a side effect of allowing DOIC to cross non-supporting agents.
> If we didn't allow that, we could make DOIC support and capabilites
> negotiation happen as part of the CAR exchange. )
>
> ----
>
> I believe the existing text is pretty clear now (and was in -02) that
> the lifetime of the capability announcement is a single transaction.
>
> Does anyone object to closing this issue?
>
> Steve
>
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime
>

v2.23.0 | Report a Bug | By Email