/// The pointer identifies the octet of the original datagram's header where the error was detected (it may be in the middle of an option).
/// For example, 1 indicates something is wrong with the Type of Service, and (if there are options present) 20 indicates something is wrong with the type code of the first option.
/// Address of the gateway to which traffic for the network specified in the internet destination network field of the original datagram's data should be sent.
/// If the gateway processing a datagram finds the time to live field is zero it must discard the datagram.
/// The gateway may also notify the source host via the time exceeded message.
/// </summary>
TimeExceededTimeToLive=0x0B00,
/// <summary>
/// RFC 792.
/// If a host reassembling a fragmented datagram cannot complete the reassembly due to missing fragments within its time limit it discards the datagram,
/// and it may send a time exceeded message.
/// If fragment zero is not available then no time exceeded need be sent at all.
/// </summary>
TimeExceededFragmentReassembly=0x0B01,
/// <summary>
/// RFC 792.
/// If the gateway or host processing a datagram finds a problem with the header parameters such that it cannot complete processing the datagram it must discard the datagram.
/// One potential source of such a problem is with incorrect arguments in an option.
/// The gateway or host may also notify the source host via the parameter problem message.
/// This message is only sent if the error caused the datagram to be discarded.
/// </summary>
ParameterProblemPointerIndicatesTheError=0x0C00,
/// <summary>
/// RFC 792.
///
/// <para>
/// A gateway may discard internet datagrams if it does not have the buffer space needed to queue the datagrams for output to the next network on the route to the destination network.
/// If a gateway discards a datagram, it may send a source quench message to the internet source host of the datagram.
/// A destination host may also send a source quench message if datagrams arrive too fast to be processed.
/// The source quench message is a request to the host to cut back the rate at which it is sending traffic to the internet destination.
/// The gateway may send a source quench message for every message that it discards.
/// On receipt of a source quench message, the source host should cut back the rate at which it is sending traffic to the specified destination
/// until it no longer receives source quench messages from the gateway.
/// The source host can then gradually increase the rate at which it sends traffic to the destination until it again receives source quench messages.
/// </para>
///
/// <para>
/// The gateway or host may send the source quench message when it approaches its capacity limit rather than waiting until the capacity is exceeded.
/// This means that the data datagram which triggered the source quench message may be delivered.
/// The data received in the echo message must be returned in the echo reply message.
/// </para>
///
/// <para>
/// The identifier and sequence number may be used by the echo sender to aid in matching the replies with the echo requests.
/// For example, the identifier might be used like a port in TCP or UDP to identify a session, and the sequence number might be incremented on each echo request sent.
/// The echoer returns these same values in the echo reply.
/// </para>
///
/// <para>
/// Code 0 may be received from a gateway or a host.
/// </para>
/// </summary>
Echo=0x0800,
/// <summary>
/// RFC 792.
/// <para>
/// The data received in the echo message must be returned in the echo reply message.
/// </para>
///
/// <para>
/// The identifier and sequence number may be used by the echo sender to aid in matching the replies with the echo requests.
/// For example, the identifier might be used like a port in TCP or UDP to identify a session, and the sequence number might be incremented on each echo request sent.
/// The echoer returns these same values in the echo reply.
/// </para>
///
/// <para>
/// Code 0 may be received from a gateway or a host.
/// </para>
/// </summary>
EchoReply=0x0000,
/// <summary>
/// RFC 792
/// <para>
/// The data received (a timestamp) in the message is returned in the reply together with an additional timestamp.
/// The timestamp is 32 bits of milliseconds since midnight UT.
/// </para>
///
/// <para>
/// If the time is not available in miliseconds or cannot be provided with respect to midnight UT
/// then any time can be inserted in a timestamp provided the high order bit of the timestamp is also set to indicate this non-standard value.
/// </para>
///
/// <para>
/// The identifier and sequence number may be used by the echo sender to aid in matching the replies with the requests.
/// For example, the identifier might be used like a port in TCP or UDP to identify a session, and the sequence number might be incremented on each request sent.
/// The destination returns these same values in the reply.
/// </para>
///
/// <para>
/// Code 0 may be received from a gateway or a host.
/// </para>
/// </summary>
Timestamp=0x0D00,
/// <summary>
/// RFC 792
/// <para>
/// The data received (a timestamp) in the message is returned in the reply together with an additional timestamp.
/// The timestamp is 32 bits of milliseconds since midnight UT.
/// </para>
///
/// <para>
/// If the time is not available in miliseconds or cannot be provided with respect to midnight UT
/// then any time can be inserted in a timestamp provided the high order bit of the timestamp is also set to indicate this non-standard value.
/// </para>
///
/// <para>
/// The identifier and sequence number may be used by the echo sender to aid in matching the replies with the requests.
/// For example, the identifier might be used like a port in TCP or UDP to identify a session, and the sequence number might be incremented on each request sent.
/// The destination returns these same values in the reply.
/// </para>
///
/// <para>
/// Code 0 may be received from a gateway or a host.
/// </para>
/// </summary>
TimestampReply=0x0E00,
/// <summary>
/// RFC 792.
/// <para>
/// This message may be sent with the source network in the IP header source and destination address fields zero (which means "this" network).
/// The replying IP module should send the reply with the addresses fully specified.
/// This message is a way for a host to find out the number of the network it is on.
/// </para>
///
/// <para>
/// The identifier and sequence number may be used by the echo sender to aid in matching the replies with the requests.
/// For example, the identifier might be used like a port in TCP or UDP to identify a session, and the sequence number might be incremented on each request sent.
/// The destination returns these same values in the reply.
/// </para>
///
/// <para>
/// Code 0 may be received from a gateway or a host.
/// </para>
/// </summary>
InformationRequest=0x0F00,
/// <summary>
/// RFC 792.
/// <para>
/// This message may be sent with the source network in the IP header source and destination address fields zero (which means "this" network).
/// The replying IP module should send the reply with the addresses fully specified.
/// This message is a way for a host to find out the number of the network it is on.
/// </para>
///
/// <para>
/// The identifier and sequence number may be used by the echo sender to aid in matching the replies with the requests.
/// For example, the identifier might be used like a port in TCP or UDP to identify a session, and the sequence number might be incremented on each request sent.
/// The destination returns these same values in the reply.
/// </para>
///
/// <para>
/// Code 0 may be received from a gateway or a host.