Normative references: Needed for the specification; specification is based on it.
Informative references: Provide background/additional information
[x] Make sure MUST/MAY/SHOULD are used correctly (see also RFC 8174):
(partially addressed in #6 )
MUST: Without this, the protocol will not work
SHOULD: Should do this unless you have a very good reason not to
MAY: Try to not use "MAY", Eliot is not a big fan of it
[x] What text can be removed? Be concise. Make sure every word that is there must be there.
Feedback Juan:
[x] #14
[x] Explain why any transport or other upper-layer protocol that includes addresses from the SCION header in the checksum computation should use a pseudo header. --> Checked IPv6 RFC2460, it dies not explain why. Our section talking about this is very similar to IPv6, and we don't feel need to change this
[x] Simplify the "Life of a packet" figure, e.g., by removing all the IP addresses and listing them in a table instead, and/or having just numbers/letters as interface IDs. Over time we rewrote this section several times and I (@nicorusti ) don't feel this will make it more readable.
General feedback Eliot:
Feedback Juan:
Explain why any transport or other upper-layer protocol that includes addresses from the SCION header in the checksum computation should use a pseudo header.--> Checked IPv6 RFC2460, it dies not explain why. Our section talking about this is very similar to IPv6, and we don't feel need to change thisSimplify the "Life of a packet" figure, e.g., by removing all the IP addresses and listing them in a table instead, and/or having just numbers/letters as interface IDs.Over time we rewrote this section several times and I (@nicorusti ) don't feel this will make it more readable.