|
Hi,
Well, which operational maintenance you have in mind which
wait for the per-mobility session re-registration to come by to announce that
hey.. we are having maintenance here, please go somewhere else? Also, how long
that maintenance operation will last?
May be you can clarify that one, first.
Thanks.
Regards,
Ahmad
Hi Telemaco,
I think
mid-session redirection scenario makes some sense and should be taken into
account. Some reasons have been given in section 4.2 of
"draft-korhonen-netext-redirect-ps-00" (e.g. maintenance operation, abrupt
change of load condition etc). There is some other mid-redirection scenario,
for example, the failure of path between MAG and rfLMA can result
in all mobility sessions of the MNs attached on the MAG corrupt. These
sessions should be correctly redirected to r2LMA to mitigate
avalanche.
BR
Jinwei
Hi,
I support
the adoption of this ID. I wonder however if the mid-session redirection
described in section 5.5.2 brings more advantages than complexity. The
authors may want to comment on this.
Thanks,
Telemaco
De :
netext-bounces at ietf.org [mailto:netext-bounces at ietf.org] De la part de
Basavaraj.Patil at nokia.com
Envoyé : jeudi 8 octobre 2009
14:36
À :
netext at ietf.org
Objet : [netext] Consensus call to
adopt I-D: draft-korhonen-netext-redirect as WG
doc
One of the Netext WG milestones
is:
Sep
2009
Initial WG draft on LMA Redirection
At IETF75, I-D
draft-korhonen-netext-redirect was accepted as the
baseline to be adopted as the
doc. Process requires that we also run
the consensus call on the WG
ML.
The I-D: Runtime LMA Assignment
Support for Proxy Mobile IPv6,
draft-korhonen-netext-redirect-04.txt
has now been posted and this is
a consensus call for its
adoption as WG doc.
Please respond by Oct 15th, 09.
|