Issue#108: Remove last remaining occurrences of HOST_TO_NET and NET_TO_HOST from spec.#117
Conversation
jafingerhut
left a comment
There was a problem hiding this comment.
Looks reasonable to me, with one minor comment.
PNA.mdk
Outdated
| | Description | next by | packet(s) | | ||
| +:--------------+:--------------+:-----------------------+ | ||
| | packet from | main | Zero or more mirrored | | ||
| | network port | | packets | |
There was a problem hiding this comment.
In the "Resulting packet(s)" column, would it be more accurate to expand it to something like the following text?
Zero or more mirrored packets, plus at most one copy of the original packet (which may be marked for recirculation).
There was a problem hiding this comment.
Are the mirrored packets also allowed to be recirculated? I would think yes, as it may be the only way to support broadcast traffic to a number of VMs larger than the target's maximum mirror slots.
Is the original packet always emitted albeit possibly marked for drop? (The comment in the P4 file says it is dropped after the end of the control block.)
If both the above are true, I would suggest this text:
Original packet which may be recirculated or marked for drop, and zero or more mirrored packets some of which may be recirculated.
I'm also adding a forward reference to the packet mirroring section (§6.8) in the corresponding paragraph just after this table.
ca8609a to
e35bcde
Compare
|
Text changed as suggested, and forward reference added. |
Also move the obsolete packet path figures in to the
historicalsubdirectory - these will eventually need to be redone as per the TBD in the text (§ 6 and appendix D).Was able to regenerate the HTML & PDF and the updated table 1 looks OK.
With these changes there are no remaining occurrences of HOST_TO_NET or NET_TO_HOST in the repository.
Edit: link issue #108