[midcom] Re: AD evaluation comments on draft-ietf-midcom-mib-07

Magnus Westerlund <magnus.westerlund@ericsson.com> Fri, 28 July 2006 07:51 UTC

Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6N7e-0000zL-8a; Fri, 28 Jul 2006 03:51:02 -0400
Received: from [] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6N7c-0000zG-DK for midcom@ietf.org; Fri, 28 Jul 2006 03:51:00 -0400
Received: from mailgw4.ericsson.se ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6N7Y-0002RZ-NV for midcom@ietf.org; Fri, 28 Jul 2006 03:51:00 -0400
Received: from esealmw126.eemea.ericsson.se (unknown []) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 1738E6E0002; Fri, 28 Jul 2006 09:50:56 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 28 Jul 2006 09:50:55 +0200
Received: from [] ([]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 28 Jul 2006 09:50:54 +0200
Message-ID: <44C9C1DE.4090404@ericsson.com>
Date: Fri, 28 Jul 2006 09:50:54 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird (Windows/20060516)
MIME-Version: 1.0
To: Juergen Quittek <quittek@netlab.nec.de>
References: <44C77E8B.2090509@ericsson.com> <A948C73A4E452D02087ECB28@[]> <44C8ED12.3060900@ericsson.com> <C9125AF6718D234E58A9C1E7@[]>
In-Reply-To: <C9125AF6718D234E58A9C1E7@[]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Jul 2006 07:50:54.0464 (UTC) FILETIME=[8DCE5000:01C6B21A]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: midcom@ietf.org, Martin Stiemerling <stiemerling@netlab.nec.de>, Pyda Srisuresh <srisuresh@yahoo.com>
Subject: [midcom] Re: AD evaluation comments on draft-ietf-midcom-mib-07
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: midcom.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=subscribe>
Errors-To: midcom-bounces@ietf.org

Juergen Quittek wrote:
> Hi Magnus,
> --On 27.07.2006 18:42 Uhr +0200 Magnus Westerlund wrote:
>> Hi,
>> Thanks for the quick reply. I do have some follow up below.
>> When these have been resolved please submit a new document.
>> Then I should be able to put it on IETF last call so it will
>> be ready to go to IESG when I am back from my vacation.
>> Juergen Quittek wrote:
>>>> 1. midcomGroupLifetime:
>>>> I wonder why this object is defined as providing the longest
>>>> time until something expires. Would not the MIDCOM client be
>>>> more interested in the shortest time until something in the
>>>> group expires?
>>> Groups in the MIDOCOM MIB only exist conceptually.
>>> There are no explicit group instances containing any state
>>> beyond the the state contained in members.
>>> Please see the DESCRIPTION clause of midcomGroupTable:
>>>         Entries in this table are created or removed
>>>         implicitly when entries in the midcomRuleTable are
>>>         created or removed, respectively.  A group entry
>>>         in this table only exists as long as there are
>>>         member rules of this group in the midcomRuleTable.
>>> Groups are instantiated by instantiating the first member
>>> and they are removed by removing the last remaining member.
>>> Therefore, the lifetime of the group is the maximum of all member
>>> lifetimes.
>> Yes, you are correct that the groups lifetime is the maximum of
>> the included rules. However from a usability point of view it seems
>> that the minimum would be better. However if the WG thinks this is
>> fine, then I will not persist with my point of view.
> When we discussed this in the WG, there was consensus that
> groups provide shortcuts to actions on all members.
> We consider a group to be existent as long as there is a member.
> Hence, object midcomGroupLifetime contains the (expected) lifetime
> of the group.
> I see no problem with adding another object that provides what
> you suggest, maybe called groupShortestMemberLifetime.
> But so far, the group has not seen the need for it.

Okay, lets leave things as they are. I think my case is in most cases 
not relevant as it will be the MIDCOM client that has created the group 
and can easily keep track of the shortest itself. And in extreme cases 
when it doesn't have this state it can easily either retrieve it or set 
the midcomGroupLifetime to be certain that all rules in the group has 
the same lifetime.

I am fine with the other changes you propose. Please submit a new draft 
with these changes.


Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com

midcom mailing list