rmt-2----Page:8
1 2 3 4 5 6 7 8 9 10 11 12
|
Sender Protection from Receiver NACK/ACK replay Make use of sequence number in NORM message header 16 bits, but receiver feedback is sparse Need to maintain state only for receivers that have NACKed within current sender repair window Replay of NACKs from outside of repair window inflict little harm Sender may transmit limited NORM_CMD(SQUELCH) or ignore. Similar for congestion control feedback and other receiver ACK messages. RECOMMEND use of encryption to minimize chance of complex attacks on long-lived NORM sessions. But would likely rekey before repair window space (objectId::fecBlockId::symbolId) wraps anyway |