問題文
A session has been up for hours when the far end suddenly tears it down, and the log says the leading 16 octets of one arriving header were not all ones as the specification requires. The operator wants the name of the field that was wrong. Separately the operator is watching a capture and sees the one message type that carries reachability and the attributes that go with it, as opposed to the type that only negotiates capabilities at startup. Which pair names the message type and the bad field?
選択肢
- Junos automatically emits this open message, and each one of the headers opens with the version field
- Junos automatically emits this open message, and each one of the headers opens with the marker field
- Junos automatically emits this update message, and each one of the headers opens with the marker field
- Junos automatically emits this update message, and each one of the headers opens with the version field