Subject: Re: [netlmm] WG Last-Call on Heartbeat Mechanism for Proxy MobileIPv6 ( draft-ietf-netlmm-pmipv6-heartbeat)

From: Vijay Devarapalli <[email-masked]>
Date: Tue, 09 Dec 2008 17:58:33 -0800

Koodli, Rajeev wrote:

>>>  If a PMIPv6 node restarts and looses PMIPv6 session state, it
> SHOULD
>>>  send an unsolicited Heartbeat Response message with an incremented
>>>   Restart Counter to all the PMIPv6 nodes that had previously
>>>   established PMIPv6 sessions.
>> To be able to do this the PMIPv6 node must store the list of its
> active
>> PMIPv6 peers into the non-volatile memory. As the non-volatile memory
> is
>> mentioned in the context of a Restart Counter, maybe it should be also
>> mentioned here?
> 
> [RKo:>] That's okay with me.

Modified the paragraph as follows

    If a PMIPv6 node restarts and looses PMIPv6 session state, it SHOULD
    send an unsolicited Heartbeat Response message with an incremented
    Restart Counter to all the PMIPv6 nodes that had previously
    established PMIPv6 sessions.  Note that this is possible only when
    the PMIPv6 node stores information about the peers in non-volatile
    memory.  The unsolicited Heartbeat Response message allows the peer
    PMIPv6 nodes to quickly discover the restart.

>> Would it make sense to mandate that the PMIP6 must clear the
> corresponding
>> BCEs/BULs when it detects that the peer node re-booted? In the current
>> thext the action upon detection of a peer's re-boot is out of scope.
> I'm
>> not sure why is that.
> 
> [RKo:>] A node may take actions all of which may not be specified in a
> spec. 
> This is a spec about reachability and failure detection. If it were also
> about actions that follow failure detection, we could add procedures.
> 
> However, adding just a sentence that BCEs/BULs should be cleared seems
> okay. 

Agree. Added the following paragraph to section 3

    If a PMIPv6 node has detected that a peer PMIPv6 node has failed or
    restarted without retaining the PMIPv6 session state, it should mark
    the corresponding binding update list or binding cache entries as
    invalid.  The PMIPv6 node may also take other actions which are
    outside the scope of this document.

Vijay

> 
> Regards,
> 
> -Rajeev
> 
>> domagoj
>>
>>
>>> -----Original Message-----
>>> From: [email-masked]
>>> [mailto:[email-masked]] On Behalf Of Soininen Jonne
>>> (NSN FI/Espoo)
>>> Sent: 10. studeni 2008 22:04
>>> To: [email-masked]
>>> Subject: [netlmm] WG Last-Call on Heartbeat Mechanism for
>>> Proxy Mobile IPv6 ( draft-ietf-netlmm-pmipv6-heartbeat)
>>>
>>> Hello Netlmm-WG,
>>>
>>> The netlmm WG chairs would like to announce the following last call.
>>>
>>> Title:  Heartbeat Mechanism for Proxy Mobile IPv6
>>> Draft:  draft-ietf-netlmm-pmipv6-heartbeat
>>> Start:  10.11.2008, 11pm EET
>>> Due:    24.11.2008, 11pm EET
>>> Duration: 2 weeks
>>>
>>> Please, review the draft and provide comments on the list.
>>>
>>> Regards,
>>>
>>> Vidya & Jonne.
>>>
>>> --
>>> Jonne Soininen
>>> Nokia Siemens Networks
>>>
>>> Tel: +358 40 527 46 34
>>> E-mail: [email-masked]
>>>
>>>
>>> _______________________________________________
>>> netlmm mailing list
>>> [email-masked]
>>> https://www.ietf.org/mailman/listinfo/netlmm
>>>
>> _______________________________________________
>> netlmm mailing list
>> [email-masked]
>> https://www.ietf.org/mailman/listinfo/netlmm
> _______________________________________________
> netlmm mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/netlmm

_______________________________________________
netlmm mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/netlmm