|
Hi,
after re-reading the draft come up with the comment on
"Discard" action in "Flow Identification
Mobility Option"
I suggest either to extend the paragraph in the
section 4.2 or add a separate subsection clarifying behavior of MN and HA before
and after the "Discard" action was issued by
MN.
Below are the issues which are proposed to be addressed
in the text.
1.The case when installed FID represent ranges of port numbers and
IP addresses. If MN decides to discard a particular flow within the range then
before that a correspondent FID should be installed in the HA. Otherwise
"136 FID not found" will be returned from
HA.
2. Specify the time interval for how long time the "Discard" state
will be active in HA. This is necessary because there is no "un-discard"
message sent from MN.
3. Add
a disclaimer that for some protocols, like TCP, "Discard" action may lead to
hanging up the connection at CN and should be used
responsibly.
Regards
Yuri
|