Re: [Mipshop] transient binding draft update
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mipshop] transient binding draft update



Hi Vijay,

The following sentence is very long and I have problem following what it
is trying to say.

   Some implementation specific solutions, such as static configuration
   on the LMA to accept uplink packets from both the old MAG and the new
   MAG for a short duration during the handover and buffering and the
new
   MAG, can help to address some of the issues identified in
   this draft, which is discussed in Appendix B.


Regards,
Ahmad
 

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay at wichorus.com] 
> Sent: Wednesday, September 16, 2009 3:30 PM
> To: Muhanna, Ahmad (RICH1:2H10); Marco Liebsch
> Cc: mipshop at ietf.org
> Subject: RE: [Mipshop] transient binding draft update
> 
> Hello,
> 
> I looked at the emails, including the latest draft version 
> that Marco sent to me offline. I would still like to see the 
> following change done.
> 
> OLD:
> 
>    Some implementation specific solutions, such as static 
> configuration
>    and buffering, can help to address some of the issues identified in
>    this draft, which is discussed in Appendix B.  A dynamic 
> solution by
>    means of the proposed protocol operation helps to optimize the
>    performance for a variety of handover situations and 
> different radio
>    characteristics.
> 
> NEW:
> 
>    Some implementation specific solutions, such as static 
> configuration
>    on the LMA to accept uplink packets from both the old MAG 
> and the new
>    MAG for a short duration during the handover and buffering 
> and the new
>    MAG, can help to address some of the issues identified in
>    this draft, which is discussed in Appendix B.  A dynamic 
> solution by
>    means of the proposed protocol operation helps to optimize the
>    performance for a variety of handover situations and 
> different radio
>    characteristics.
> 
> No changes required in appendix B.
> 
> After this change, we are good to go.
> 
> Vijay
> 

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.