Opened 11 years ago

#15 new enhancement

suggestion for naming UPDATE packets

Reported by: thomas.r.henderson@… Owned by: thomas.r.henderson@…
Priority: major Milestone:
Component: rfc5206-bis Version:
Severity: - Keywords:
Cc:

Description

From Baris Boyvat: "There is always three UPDATE packet sent for a mobility event. In HIPL
this fact was not explicitly used in the implementation before, which
made the implementation quite complex. I would suggest to explicitly
quality the UPDATE packets numbers, etc. UPDATE1, UPDATE2, UPDATE3
which would in a way force people to think in that terms.

Otherwise, when dealing with different UPDATE scenarios, SEQ, ACK handling,
retransmissions,etc conceptualization become very difficult. Actually
if possible,
I would suggest to nicely separate these concepts so that they can be
easily modularized in an implementation. I'm not sure, it's common for RFCs
but this can be done in a "implementation recommendation" form."

Change History (0)

Note: See TracTickets for help on using tickets.