Re: [netext] AD review of draft-ietf-netext-bulk-re-registration

[Sri Gundavelli <[e-mail]>]

Hi Jari:



On 11/22/11 11:00 AM, "Jari Arkko" <[e-mail]> wrote:

> Sri,
> 
>> 
>> The first quoted paragraph seems to claim that both sides can group devices
>> per their own desires. This does not seem to be supported by the rest of the
>> specification, as the LMA will override whatever suggestion was made by the
>> MAG. This may be fine, but I would change the first paragraph as follows:
>> 
> 
>> We allowed both the nodes to perform group operations. A given session may
>> be assigned a MAG-specific group identifier and also an LMA-specific group
>> identifier. Probably it needs corrections in couple of places and in the
>> illustration.
>> 
>> 
>> 
> 
> You say you allowed, but I don't actually see the functionality. You can have
> the MAG set it, you can have LMA set it, but it is not possible for *both* to
> set it. If the LMA wants to dictate group IDs, then the IDs that the MAG used
> no longer can be used. Or am I missing something?
> 

My intention was to support the scenario to perform binding operations on
nodes that are hosted on the same application blade/module of the MAG, or on
the LMA. For example, when the MAG creates sessions for two mobile nodes
(Ex: MN-1 and MN-2), both these nodes may be hosted on a given blade of the
MAG, while those sessions on LMA may be hosted on two different blades. So,
the group ID's for these nodes will be MN-1 (Mag-Id1, Lma-Id1), MN-2
(Mag-Id1, LMA-Id2). The binding operations can be now performed on Mag-Id1,
Lma-Id1, or Lma-Id2.  I agree, this part of the text is not clear and should
be updated. But, the option can be carried on both the directions, the
BCE/BUL entries needs to store both the id's, binding operation's scope is
always a single Id present in the identifier, protocol negotiation related
text is where there is some ambiguity. So, might need to update in just
couple of places, that's all. But, I agree, the current text is bit unclear
on this aspect. I can quickly address this comment and there is a long
weekend not too far :)



Regards
Sri
 




> Jari
>