|
I read the draft and it looks good. Just have a few comments
(mostly minor ones): Comment 1 In page 10, the term "Binding Reference sub-option"
is used for the first time before it is defined. It might be useful to say that
it will be defined later... Comment 2 Section 5.2.2.2 says: "To modify an existing flow binding the mobile node
MUST send a binding update with a flow identification option, with the FID
field set to one of the FID values already in the list of flow binding
entries." I might have missed something, but in this case, what
prevents the HA from sending a failure Status message "135 FID already in
use" as mentioned in Section 5.3.2.1: "If the FID field of the flow identification option is
already present in the list of flow binding entries for this mobile node, the
home agent MUST reject this flow binding add request by copying the flow
identification option in the BA, and setting the Status field to 135 (FID
already in use)." In other words, how would the receiver distinguish between a
modify request (which should not fail) and an add request with a used FID
(which should fail)? Comment 3 In Sections 5.3.2.2 and 5.3.3, the "FID not found"
Status is set to 135, whereas the table in Page 9 says it is 136. Comment 4 Section 4.2.2 says "17-32 reserved for Flow Description
formats". But the section on IANA considerations says 16-32. Minor comments: 1. Page 6: "ant-replay" ->
"anti-replay" 2. Page 9: Under FID: "an 16-bit" -> "a
16-bit" 3. End of pg 12: "refresing" ->
"refreshing" 4. Pg 17: "Mobiles nodes" -> "Mobile
nodes" 5. Pg 18: "Status filed" -> "Status
field" 6. Section 5.2.4: "bingings" ->
"bindings" 7. Section 5.3.2.2: "processes" ->
"process" 8. Section 5.3.3: "slow binding entries the, "
-> "flow binding entries, the" 9. Section 5.3.6: End of 1st paragraph: there seems to be an
extra "when" |