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

[Sri Gundavelli <[e-mail]>]

> 
> There is something wrong with the above text. B must be set in the session
> establishment, but not with "binding update operations with group specific
> scope"? (And what are those?)
> 

Hi Jari:

Thanks for the review.

There are two cases here:

1.) Establishment of the initial session for a given mobile node as in today
- the approach of group id exchange for that session to be established

2.) Performing a bulk binding operation on a group of mobile nodes/sessions
that are part of a given group - Ex: Periodic BU for lifetime extension

In both these cases, there is a PBU and there is the Group Identifier
option. In #1, the MAG presents the group identifier for that mobile node,
so the LMA can associate the group id with that session.  In #2, the MAG
wants the binding operation to be performed on a set of nodes/sessions
identified by the group id, that was previously exchanged.

The (B) flag for #1 is enabled. It serves as the means to request the LMA to
enable bulk binding operation for a given mobility session. The LMA can
accept the request, set the (B) flag in the PBA and return its own local
group id for that session. Or, simply can decide not to enable bulk binding
update feature for that session, by turning of the (B) flag in the PBA.

In case of #2, once the sessions are established and associated with a group
id, the Group Identifier in the option alone is sufficient, there is no need
for toggling the (B) flag in the PBU/PBA.

We can make the logic work, eliminating the (B) flag entirely, even for #1,
but the logic gets complex, looking at individual session identifier
presence (Mobile Node identifier option ..IPv4 Home Address option) ..etc.

  

Regards
Sri


On 1/3/12 12:33 AM, "Jari Arkko" <[e-mail]> wrote:

> Sri:
> 
> Thanks for the update! I have reviewed the changes and they look good to me
> with one exception (below). I have in any case requested an IETF Last Call to
> be initiated and expect that you fix the remaining issues by issuing yet
> another draft quickly.
> 
> But the changes are pretty big -- it would also be useful if members of the WG
> reviewed the document while it is in the Last Call.
> 
>> o  When sending the Mobile Node Group Identifier option in the
>>   binding update messages related to the individual session
>>   establishment, the Bulk-Binding-Update (B) flag in the request
>>   MUST be set to a value of (1).  However, when initiating any
>>   binding update operations with group specific scope, the Bulk-
>>   Binding-Update (B) flag in the request MUST always be set to a
>>   value of (0), with the Mobile Node Group Identifier option present
>>   in the request.
> 
> There is something wrong with the above text. B must be set in the session
> establishment, but not with "binding update operations with group specific
> scope"? (And what are those?)
> 
> Jari
>