Showing:

Annotations
Attributes
Diagrams
Facets
Source
Used by
Main schema Network_Packet_Object.xsd
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This schema was originally developed by The MITRE Corporation. The CybOX XML Schema implementation is maintained by The MITRE Corporation and developed by the open CybOX Community. For more information, including how to get involved in the effort and how to submit change requests, please visit the CybOX website at http://cybox.mitre.org.
Element PacketObj:Network_Packet
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Network_Packet object provides the definition of a network packet based on the TCP/IP model/Internet protocol suite. In the TCP/IP stack, "packet" is generally defined as IP header plus payload, but we also include the LinkLayer from the OSI model, which defines the physical network interfaces and routing protocols. The application layer has not yet been defined.
Diagram
Diagram Network_Packet_Object_xsd.tmp#NetworkPacketObjectType_Link_Layer Network_Packet_Object_xsd.tmp#NetworkPacketObjectType_Internet_Layer Network_Packet_Object_xsd.tmp#NetworkPacketObjectType_Transport_Layer Network_Packet_Object_xsd.tmp#NetworkPacketObjectType
Type PacketObj:NetworkPacketObjectType
Type hierarchy
Children PacketObj:Internet_Layer, PacketObj:Link_Layer, PacketObj:Transport_Layer
Source
 
<xs:element name="Network_Packet" type="PacketObj:NetworkPacketObjectType">
  <xs:annotation>
    <xs:documentation>The Network_Packet object provides the definition of a network packet based on the TCP/IP model/Internet protocol suite. In the TCP/IP stack, "packet" is generally defined as IP header plus payload, but we also include the LinkLayer from the OSI model, which defines the physical network interfaces and routing protocols. The application layer has not yet been defined.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NetworkPacketObjectType / PacketObj:Link_Layer
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
Diagram
Type PacketObj:LinkLayerType
Children PacketObj:Logical_Protocols, PacketObj:Physical_Interface
Source
Element PacketObj:LinkLayerType / PacketObj:Physical_Interface
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Physical Interface characterizes one hardware interface of a link layer connection.
Diagram
Diagram Network_Packet_Object_xsd.tmp#PhysicalInterfaceType_Ethernet Network_Packet_Object_xsd.tmp#PhysicalInterfaceType
Type PacketObj:PhysicalInterfaceType
Children PacketObj:Ethernet
Source
 
<xs:element name="Physical_Interface" type="PacketObj:PhysicalInterfaceType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Physical Interface characterizes one hardware interface of a link layer connection.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:PhysicalInterfaceType / PacketObj:Ethernet
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Ethernet sends network packets from the sending host to one or more receiving hosts. (REF: IEEE 802.3; http://wiki.wireshark.org/Ethernet).
Diagram
Diagram Network_Packet_Object_xsd.tmp#EthernetInterfaceType_Ethernet_Header Network_Packet_Object_xsd.tmp#EthernetInterfaceType
Type PacketObj:EthernetInterfaceType
Children PacketObj:Ethernet_Header
Source
 
<xs:element name="Ethernet" type="PacketObj:EthernetInterfaceType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Ethernet sends network packets from the sending host to one or more receiving hosts. (REF: IEEE 802.3; http://wiki.wireshark.org/Ethernet).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:EthernetInterfaceType / PacketObj:Ethernet_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The ethernet header includes information such as source MAC address, destination MAC address, and more.
Diagram
Diagram Network_Packet_Object_xsd.tmp#EthernetHeaderType_Destination_MAC_Addr Network_Packet_Object_xsd.tmp#EthernetHeaderType_Source_MAC_Addr Network_Packet_Object_xsd.tmp#EthernetHeaderType_Type_Or_Length Network_Packet_Object_xsd.tmp#EthernetHeaderType_Checksum Network_Packet_Object_xsd.tmp#EthernetHeaderType
Type PacketObj:EthernetHeaderType
Children PacketObj:Checksum, PacketObj:Destination_MAC_Addr, PacketObj:Source_MAC_Addr, PacketObj:Type_Or_Length
Source
 
<xs:element name="Ethernet_Header" type="PacketObj:EthernetHeaderType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The ethernet header includes information such as source MAC address, destination MAC address, and more.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:EthernetHeaderType / PacketObj:Destination_MAC_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Destination MAC Addr characterizes the destination MAC Address of the ethernet frame.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Destination_MAC_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Destination MAC Addr characterizes the destination MAC Address of the ethernet frame.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:EthernetHeaderType / PacketObj:Source_MAC_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Source MAC Addr characterizes the source MAC Address of the ethernet frame.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Source_MAC_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Source MAC Addr characterizes the source MAC Address of the ethernet frame.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:EthernetHeaderType / PacketObj:Type_Or_Length
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Type or Length characterizes either the length of the ethernet frame or the protocol type of the network layer.
Diagram
Diagram Network_Packet_Object_xsd.tmp#TypeLengthType_Length Network_Packet_Object_xsd.tmp#TypeLengthType_Internet_Layer_Type Network_Packet_Object_xsd.tmp#TypeLengthType
Type PacketObj:TypeLengthType
Children PacketObj:Internet_Layer_Type, PacketObj:Length
Source
 
<xs:element name="Type_Or_Length" type="PacketObj:TypeLengthType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Type or Length characterizes either the length of the ethernet frame or the protocol type of the network layer.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TypeLengthType / PacketObj:Length
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Length characterizes the length of the ethernet frame.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Length" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Length characterizes the length of the ethernet frame.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TypeLengthType / PacketObj:Internet_Layer_Type
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
two-octet field in an Ethernet frame. specifies protocol encapsulated in the payload of ethernet frame.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IANAEtherType_datatype Network_Packet_Object_xsd.tmp#IANAEtherType
Type PacketObj:IANAEtherType
Type hierarchy
Source
 
<xs:element name="Internet_Layer_Type" type="PacketObj:IANAEtherType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>two-octet field in an Ethernet frame. specifies protocol encapsulated in the payload of ethernet frame.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:EthernetHeaderType / PacketObj:Checksum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Checksum characterizes the Frame Check sequence of an ethernet frame.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Checksum" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Checksum characterizes the Frame Check sequence of an ethernet frame.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:LinkLayerType / PacketObj:Logical_Protocols
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Logical Protocols characterizes the logical protocol of a link layer connection. One example of a logical protocol is ARP.
Diagram
Diagram Network_Packet_Object_xsd.tmp#LogicalProtocolType_ARP_RARP Network_Packet_Object_xsd.tmp#LogicalProtocolType_NDP Network_Packet_Object_xsd.tmp#LogicalProtocolType
Type PacketObj:LogicalProtocolType
Children PacketObj:ARP_RARP, PacketObj:NDP
Source
 
<xs:element name="Logical_Protocols" type="PacketObj:LogicalProtocolType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Logical Protocols characterizes the logical protocol of a link layer connection. One example of a logical protocol is ARP.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:LogicalProtocolType / PacketObj:ARP_RARP
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ARP is a logical protocol used for resolution of network layer addresses (e.g., IP addresses) into link layer addresses (e.g., MAC addresses). RARP is a logical protocol used by a host computer to request its network layer address when it has its link layer address.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ARPType_Hardware_Addr_Type Network_Packet_Object_xsd.tmp#ARPType_Proto_Addr_Type Network_Packet_Object_xsd.tmp#ARPType_Hardware_Addr_Size Network_Packet_Object_xsd.tmp#ARPType_Proto_Addr_Size Network_Packet_Object_xsd.tmp#ARPType_Op_Type Network_Packet_Object_xsd.tmp#ARPType_Sender_Hardware_Addr Network_Packet_Object_xsd.tmp#ARPType_Sender_Protocol_Addr Network_Packet_Object_xsd.tmp#ARPType_Recip_Hardware_Addr Network_Packet_Object_xsd.tmp#ARPType_Recip_Protocol_Addr Network_Packet_Object_xsd.tmp#ARPType
Type PacketObj:ARPType
Children PacketObj:Hardware_Addr_Size, PacketObj:Hardware_Addr_Type, PacketObj:Op_Type, PacketObj:Proto_Addr_Size, PacketObj:Proto_Addr_Type, PacketObj:Recip_Hardware_Addr, PacketObj:Recip_Protocol_Addr, PacketObj:Sender_Hardware_Addr, PacketObj:Sender_Protocol_Addr
Source
 
<xs:element name="ARP_RARP" type="PacketObj:ARPType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>ARP is a logical protocol used for resolution of network layer addresses (e.g., IP addresses) into link layer addresses (e.g., MAC addresses). RARP is a logical protocol used by a host computer to request its network layer address when it has its link layer address.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ARPType / PacketObj:Hardware_Addr_Type
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Characterizes the type of hardware address specified in an ARP message.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IANAHardwareType_datatype Network_Packet_Object_xsd.tmp#IANAHardwareType
Type PacketObj:IANAHardwareType
Type hierarchy
Source
 
<xs:element name="Hardware_Addr_Type" type="PacketObj:IANAHardwareType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Characterizes the type of hardware address specified in an ARP message.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ARPType / PacketObj:Proto_Addr_Type
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ProtoAddrType characterizes the type of protocol address being mapped. For IPv4 addresses, value = 0x0800.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IANAEtherType_datatype Network_Packet_Object_xsd.tmp#IANAEtherType
Type PacketObj:IANAEtherType
Type hierarchy
Source
 
<xs:element name="Proto_Addr_Type" type="PacketObj:IANAEtherType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>ProtoAddrType characterizes the type of protocol address being mapped. For IPv4 addresses, value = 0x0800.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ARPType / PacketObj:Hardware_Addr_Size
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Harware_Addr_Size represents the byte size of the hardware address. For Ethernet or other IEEE 802 MAC addresses, the value is 6.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Hardware_Addr_Size" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Harware_Addr_Size represents the byte size of the hardware address. For Ethernet or other IEEE 802 MAC addresses, the value is 6.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ARPType / PacketObj:Proto_Addr_Size
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Proto_Addr_Size represents the byte size of the protocol address. IPv4 addresses = 4.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Proto_Addr_Size" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Proto_Addr_Size represents the byte size of the protocol address. IPv4 addresses = 4.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ARPType / PacketObj:Op_Type
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Op_Type characterizes the type of operation. 1 = ARP request, 2=ARP reply, 3=RARP request, 4=RARP reply.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ARPOpType_datatype Network_Packet_Object_xsd.tmp#ARPOpType
Type PacketObj:ARPOpType
Type hierarchy
Source
 
<xs:element name="Op_Type" type="PacketObj:ARPOpType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Op_Type characterizes the type of operation. 1 = ARP request, 2=ARP reply, 3=RARP request, 4=RARP reply.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ARPType / PacketObj:Sender_Hardware_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Sender_Hardware_Addr characterizes the sender's hardware address (e.g., MAC address).
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Sender_Hardware_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Sender_Hardware_Addr characterizes the sender's hardware address (e.g., MAC address).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ARPType / PacketObj:Sender_Protocol_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Sender_Protocol_Addr characterizes the sender's IP address.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Sender_Protocol_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Sender_Protocol_Addr characterizes the sender's IP address.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ARPType / PacketObj:Recip_Hardware_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Recip_Sender_Hardware Addr characterizes the recipients' hardware address (e.g., MAC address).
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Recip_Hardware_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Recip_Sender_Hardware Addr characterizes the recipients' hardware address (e.g., MAC address).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ARPType / PacketObj:Recip_Protocol_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Recip Protocol Addr characterizes the recipient's IP address.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Recip_Protocol_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Recip Protocol Addr characterizes the recipient's IP address.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:LogicalProtocolType / PacketObj:NDP
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Neighbor Discovery Protocol (NDP) is used with IPv6 to determine the link-layer addresses for neighbors. Corresponds to combination of IPv4 protocols: ARP, ICMP Router Discovery, and ICMP Redirect.
Diagram
Diagram Network_Packet_Object_xsd.tmp#NDPType_ICMPv6_Header Network_Packet_Object_xsd.tmp#NDPType_Router_Solicitation Network_Packet_Object_xsd.tmp#NDPType_Router_Advertisement Network_Packet_Object_xsd.tmp#NDPType_Neighbor_Solicitation Network_Packet_Object_xsd.tmp#NDPType_Neighbor_Advertisement Network_Packet_Object_xsd.tmp#NDPType_Redirect Network_Packet_Object_xsd.tmp#NDPType
Type PacketObj:NDPType
Children PacketObj:ICMPv6_Header, PacketObj:Neighbor_Advertisement, PacketObj:Neighbor_Solicitation, PacketObj:Redirect, PacketObj:Router_Advertisement, PacketObj:Router_Solicitation
Source
 
<xs:element name="NDP" type="PacketObj:NDPType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Neighbor Discovery Protocol (NDP) is used with IPv6 to determine the link-layer addresses for neighbors. Corresponds to combination of IPv4 protocols: ARP, ICMP Router Discovery, and ICMP Redirect.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NDPType / PacketObj:ICMPv6_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ICMPv6 Header characterizes an ICMPv6 header.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6HeaderType_Type Network_Packet_Object_xsd.tmp#ICMPv6HeaderType_Code Network_Packet_Object_xsd.tmp#ICMPv6HeaderType_Checksum Network_Packet_Object_xsd.tmp#ICMPv6HeaderType
Type PacketObj:ICMPv6HeaderType
Children PacketObj:Checksum, PacketObj:Code, PacketObj:Type
Source
 
<xs:element name="ICMPv6_Header" type="PacketObj:ICMPv6HeaderType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>ICMPv6 Header characterizes an ICMPv6 header.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6HeaderType / PacketObj:Type
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The ICMP v6 type byte specifies the type of the message. Values range from 0 to 127 (high order bit is 0) indicate an error messages; values from 128 to 255 (high order bit is 1) indicate an informational message.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Type" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The ICMP v6 type byte specifies the type of the message. Values range from 0 to 127 (high order bit is 0) indicate an error messages; values from 128 to 255 (high order bit is 1) indicate an informational message.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6HeaderType / PacketObj:Code
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The code byte value depends on the message type and provides an additional level of message granularity.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Code" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The code byte value depends on the message type and provides an additional level of message granularity.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6HeaderType / PacketObj:Checksum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Checksum characterizes the checksum information of an ICMPv6 header.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Checksum" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Checksum characterizes the checksum information of an ICMPv6 header.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NDPType / PacketObj:Router_Solicitation
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Hosts send Router Solicitations in order to prompt routers to generate Router Advertisements quickly (type=133; code=0).
Diagram
Diagram Network_Packet_Object_xsd.tmp#RouterSolicitationType_Options Network_Packet_Object_xsd.tmp#RouterSolicitationType
Type PacketObj:RouterSolicitationType
Children PacketObj:Options
Source
 
<xs:element name="Router_Solicitation" type="PacketObj:RouterSolicitationType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Hosts send Router Solicitations in order to prompt routers to generate Router Advertisements quickly (type=133; code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RouterSolicitationType / PacketObj:Options
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Router Solicitation messages include zero or more options, some of which may appear multiple times in the same message.
Diagram
Diagram Network_Packet_Object_xsd.tmp#RouterSolicitationOptionsType_Src_Link_Addr Network_Packet_Object_xsd.tmp#RouterSolicitationOptionsType
Type PacketObj:RouterSolicitationOptionsType
Children PacketObj:Src_Link_Addr
Source
 
<xs:element name="Options" type="PacketObj:RouterSolicitationOptionsType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Router Solicitation messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RouterSolicitationOptionsType / PacketObj:Src_Link_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
Diagram
Type PacketObj:NDPLinkAddrType
Children PacketObj:Length, PacketObj:Link_Layer_MAC_Addr
Source
Element PacketObj:NDPLinkAddrType / PacketObj:Length
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The length of the option (including the type and length fields) in units of 8 octets.
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The length of the option (including the type and length fields) in units of 8 octets.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NDPLinkAddrType / PacketObj:Link_Layer_MAC_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
Diagram
Type AddressObjectType
Source
Element PacketObj:NDPType / PacketObj:Router_Advertisement
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Routers send out Router Advertisement messages periodically, or in response to Router Solicitations (type=134; code=0).
Diagram
Diagram Network_Packet_Object_xsd.tmp#RouterAdvertisementType_managed_address_config_flag Network_Packet_Object_xsd.tmp#RouterAdvertisementType_other_config_flag Network_Packet_Object_xsd.tmp#RouterAdvertisementType_Cur_Hop_Limit Network_Packet_Object_xsd.tmp#RouterAdvertisementType_Router_Lifetime Network_Packet_Object_xsd.tmp#RouterAdvertisementType_Reachable_Time Network_Packet_Object_xsd.tmp#RouterAdvertisementType_Retrans_Timer Network_Packet_Object_xsd.tmp#RouterAdvertisementType_Options Network_Packet_Object_xsd.tmp#RouterAdvertisementType
Type PacketObj:RouterAdvertisementType
Children PacketObj:Cur_Hop_Limit, PacketObj:Options, PacketObj:Reachable_Time, PacketObj:Retrans_Timer, PacketObj:Router_Lifetime
Attributes
QName Type Use Annotation
managed_address_config_flag xs:boolean optional 
1-bit "Managed address configuration" flag. When set, it indicates that addresses are available via Dynamic Host Configuration Protocol. If the M flag is set, the O flag is redundant and can be ignored because DHCPv6 will return all available configuration information.
other_config_flag xs:boolean optional 
1-bit "Other configuration" flag. When set, it indicates that other configuration information is available via DHCPv6. Examples of such information are DNS-related information or information on other servers within the network.
Source
 
<xs:element name="Router_Advertisement" type="PacketObj:RouterAdvertisementType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Routers send out Router Advertisement messages periodically, or in response to Router Solicitations (type=134; code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RouterAdvertisementType / PacketObj:Cur_Hop_Limit
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
8-bit unsigned integer. The default value that should be placed in the Hop Count field of the IP header for outgoing IP packets. A value of zero means unspecified (by this router).
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Cur_Hop_Limit" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>8-bit unsigned integer. The default value that should be placed in the Hop Count field of the IP header for outgoing IP packets. A value of zero means unspecified (by this router).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RouterAdvertisementType / PacketObj:Router_Lifetime
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
16-bit unsigned integer. The lifetime associated with the default router in units of seconds. The field can contain values up to 65535 and receivers should handle any value, while the sending rules in Section 6 limit the lifetime to 9000 seconds.
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Router_Lifetime" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>16-bit unsigned integer. The lifetime associated with the default router in units of seconds. The field can contain values up to 65535 and receivers should handle any value, while the sending rules in Section 6 limit the lifetime to 9000 seconds.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RouterAdvertisementType / PacketObj:Reachable_Time
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
32-bit unsigned integer. The time, in milliseconds, between retransmitted Neighbor Solicitation messages. Used by address resolution and the Neighbor Unreachability Detection algorithm. A value of zero means unspecified (by this router).
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Reachable_Time" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>32-bit unsigned integer. The time, in milliseconds, between retransmitted Neighbor Solicitation messages. Used by address resolution and the Neighbor Unreachability Detection algorithm. A value of zero means unspecified (by this router).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RouterAdvertisementType / PacketObj:Retrans_Timer
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
32-bit unsigned integer. The time, in milliseconds, between retransmitted Neighbor Solicitation messages. Used by address resolution and the Neighbor Unreachability Detection algorithm. A value of zero means unspecified (by this router).
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Retrans_Timer" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>32-bit unsigned integer. The time, in milliseconds, between retransmitted Neighbor Solicitation messages. Used by address resolution and the Neighbor Unreachability Detection algorithm. A value of zero means unspecified (by this router).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RouterAdvertisementType / PacketObj:Options
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Neighbor Discovery messages include zero or more options, some of which may appear multiple times in the same message.
Diagram
Diagram Network_Packet_Object_xsd.tmp#RouterAdvertisementOptionsType_Src_Link_Addr Network_Packet_Object_xsd.tmp#RouterAdvertisementOptionsType_MTU Network_Packet_Object_xsd.tmp#RouterAdvertisementOptionsType_Prefix_Info Network_Packet_Object_xsd.tmp#RouterAdvertisementOptionsType
Type PacketObj:RouterAdvertisementOptionsType
Children PacketObj:MTU, PacketObj:Prefix_Info, PacketObj:Src_Link_Addr
Source
 
<xs:element name="Options" type="PacketObj:RouterAdvertisementOptionsType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Neighbor Discovery messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RouterAdvertisementOptionsType / PacketObj:Src_Link_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
Diagram
Type PacketObj:NDPLinkAddrType
Children PacketObj:Length, PacketObj:Link_Layer_MAC_Addr
Source
Element PacketObj:RouterAdvertisementOptionsType / PacketObj:MTU
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
32-bit unsigned integer. The recommended MTU for the link.
Diagram
Diagram Network_Packet_Object_xsd.tmp#NDPMTUType_Length Network_Packet_Object_xsd.tmp#NDPMTUType_MTU Network_Packet_Object_xsd.tmp#NDPMTUType
Type PacketObj:NDPMTUType
Children PacketObj:Length, PacketObj:MTU
Source
 
<xs:element name="MTU" type="PacketObj:NDPMTUType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>32-bit unsigned integer. The recommended MTU for the link.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NDPMTUType / PacketObj:Length
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The length of the MTU option type: length=1.
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The length of the MTU option type: length=1.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NDPMTUType / PacketObj:MTU
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The recommended MTU for the link. 32-bit unsigned integer.
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="MTU" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The recommended MTU for the link. 32-bit unsigned integer.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RouterAdvertisementOptionsType / PacketObj:Prefix_Info
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Prefix Info characterizes Prefix Information for Router Advertisement Options.
Diagram
Diagram Network_Packet_Object_xsd.tmp#NDPPrefixInfoType_link_flag Network_Packet_Object_xsd.tmp#NDPPrefixInfoType_addr_config_flag Network_Packet_Object_xsd.tmp#NDPPrefixInfoType_Length Network_Packet_Object_xsd.tmp#NDPPrefixInfoType_Prefix_Length Network_Packet_Object_xsd.tmp#NDPPrefixInfoType_Valid_Lifetime Network_Packet_Object_xsd.tmp#NDPPrefixInfoType_Preferred_Lifetime Network_Packet_Object_xsd.tmp#NDPPrefixInfoType_Prefix Network_Packet_Object_xsd.tmp#NDPPrefixInfoType
Type PacketObj:NDPPrefixInfoType
Children PacketObj:Length, PacketObj:Preferred_Lifetime, PacketObj:Prefix, PacketObj:Prefix_Length, PacketObj:Valid_Lifetime
Attributes
QName Type Use Annotation
addr_config_flag xs:boolean optional 
1-bit autonomous address-configuration flag. When set indicates that this prefix can be usd for stateless address configuration.
link_flag xs:boolean optional 
1-bit on-link flag. When set, indicates that this prefix can be used for on-link determintation. When not set the advertisement makes no statement about on-link or off-link properties of the prefix.
Source
 
<xs:element name="Prefix_Info" type="PacketObj:NDPPrefixInfoType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Prefix Info characterizes Prefix Information for Router Advertisement Options.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NDPPrefixInfoType / PacketObj:Length
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Length characterizes the length of the option (the number of valid leading bits in the prefix), and is represented as a 32-bit integer.
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Length characterizes the length of the option (the number of valid leading bits in the prefix), and is represented as a 32-bit integer.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NDPPrefixInfoType / PacketObj:Prefix_Length
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
8-bit unsigned integer. The number of leading bits in the Prefix that are valid. The value ranges from 0 to 128. The prefix length field provides necessary information for on-link determination (when combined with the L flag in the prefix information option).
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Prefix_Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>8-bit unsigned integer. The number of leading bits in the Prefix that are valid. The value ranges from 0 to 128. The prefix length field provides necessary information for on-link determination (when combined with the L flag in the prefix information option).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NDPPrefixInfoType / PacketObj:Valid_Lifetime
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
32-bit unsigned integer. The length of time in seconds (relative to the time the packet is sent) that the prefix is valid for the purpose of on-link determination. A value of all one bits (0xffffffff) represents infinity.
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Valid_Lifetime" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>32-bit unsigned integer. The length of time in seconds (relative to the time the packet is sent) that the prefix is valid for the purpose of on-link determination. A value of all one bits (0xffffffff) represents infinity.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NDPPrefixInfoType / PacketObj:Preferred_Lifetime
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
32-bit unsigned integer. The length of time in seconds (relative to the time the packet is sent) that addresses generated from the prefix via stateless address autoconfiguration remain preferred.
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Preferred_Lifetime" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>32-bit unsigned integer. The length of time in seconds (relative to the time the packet is sent) that addresses generated from the prefix via stateless address autoconfiguration remain preferred.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NDPPrefixInfoType / PacketObj:Prefix
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Prefix is an IP address or a prefix of an IP address.
Diagram
Diagram Network_Packet_Object_xsd.tmp#PrefixType_IPv6_Addr Network_Packet_Object_xsd.tmp#PrefixType_IP_Addr_Prefix Network_Packet_Object_xsd.tmp#PrefixType
Type PacketObj:PrefixType
Children PacketObj:IP_Addr_Prefix, PacketObj:IPv6_Addr
Source
 
<xs:element name="Prefix" type="PacketObj:PrefixType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The Prefix is an IP address or a prefix of an IP address.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:PrefixType / PacketObj:IPv6_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
IPv6 address.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="IPv6_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>IPv6 address.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:PrefixType / PacketObj:IP_Addr_Prefix
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The initial bits of an IPv6 address (these are identical for all hosts in a network) form the network's prefix. http://ipv6.com/articles/general/IPv6-Addressing.htm.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="IP_Addr_Prefix" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The initial bits of an IPv6 address (these are identical for all hosts in a network) form the network's prefix. http://ipv6.com/articles/general/IPv6-Addressing.htm.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NDPType / PacketObj:Neighbor_Solicitation
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Nodes send Neighbor Solicitations to request the link-layer address of a target node while also providing their own link-layer address to the target. Neighbor Solicitations are multicast when the node needs to resolve an address and unicast when the node seeks to verify the reachability of a neighbor (type=135; code=0).
Diagram
Diagram Network_Packet_Object_xsd.tmp#NeighborSolicitationType_Target_IPv6_Addr Network_Packet_Object_xsd.tmp#NeighborSolicitationType_Options Network_Packet_Object_xsd.tmp#NeighborSolicitationType
Type PacketObj:NeighborSolicitationType
Children PacketObj:Options, PacketObj:Target_IPv6_Addr
Source
 
<xs:element name="Neighbor_Solicitation" type="PacketObj:NeighborSolicitationType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Nodes send Neighbor Solicitations to request the link-layer address of a target node while also providing their own link-layer address to the target. Neighbor Solicitations are multicast when the node needs to resolve an address and unicast when the node seeks to verify the reachability of a neighbor (type=135; code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NeighborSolicitationType / PacketObj:Target_IPv6_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The IP address of the target of the solicitation.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Target_IPv6_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The IP address of the target of the solicitation.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NeighborSolicitationType / PacketObj:Options
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Neighbor Solicitation messages include zero or more options, some of which may appear multiple times in the same message.
Diagram
Diagram Network_Packet_Object_xsd.tmp#NeighborSolicitationOptionsType_Src_Link_Addr Network_Packet_Object_xsd.tmp#NeighborSolicitationOptionsType
Type PacketObj:NeighborSolicitationOptionsType
Children PacketObj:Src_Link_Addr
Source
 
<xs:element name="Options" type="PacketObj:NeighborSolicitationOptionsType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Neighbor Solicitation messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NeighborSolicitationOptionsType / PacketObj:Src_Link_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
Diagram
Type PacketObj:NDPLinkAddrType
Children PacketObj:Length, PacketObj:Link_Layer_MAC_Addr
Source
Element PacketObj:NDPType / PacketObj:Neighbor_Advertisement
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
A node sends Neighbor Advertisements in response to Neighbor Solicitations and sends unsolicited Neighbor Advertisements in order to (unreliably) propagate new information quickly (type=136; code=0).
Diagram
Diagram Network_Packet_Object_xsd.tmp#NeighborAdvertisementType_router_flag Network_Packet_Object_xsd.tmp#NeighborAdvertisementType_solicited_flag Network_Packet_Object_xsd.tmp#NeighborAdvertisementType_override_flag Network_Packet_Object_xsd.tmp#NeighborAdvertisementType_Target_IPv6_Addr Network_Packet_Object_xsd.tmp#NeighborAdvertisementType_Options Network_Packet_Object_xsd.tmp#NeighborAdvertisementType
Type PacketObj:NeighborAdvertisementType
Children PacketObj:Options, PacketObj:Target_IPv6_Addr
Attributes
QName Type Use Annotation
override_flag xs:boolean optional 
Override flag. When set, the O-bit indicates that the advertisement should override an existing cache entry and update the cached link-layer address.
router_flag xs:boolean optional 
Router flag. When set, the R-bit indicates that the sender is a router. The R-bit is used by Neighbor Unreachability Detection to detect a router that changes to a host.
solicited_flag xs:boolean optional 
Solicited flag. When set, the S-bit indicates that the advertisement was sent in response to a Neighbor Solicitation from the Destination address. The S-bit is used as a reachability confirmation for Neighbor Unreachability Detection.
Source
 
<xs:element name="Neighbor_Advertisement" type="PacketObj:NeighborAdvertisementType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>A node sends Neighbor Advertisements in response to Neighbor Solicitations and sends unsolicited Neighbor Advertisements in order to (unreliably) propagate new information quickly (type=136; code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NeighborAdvertisementType / PacketObj:Target_IPv6_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The IP address of the target of the advertisement.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Target_IPv6_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The IP address of the target of the advertisement.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NeighborAdvertisementType / PacketObj:Options
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Neighbor Advertisement messages include zero or more options, some of which may appear multiple times in the same message.
Diagram
Diagram Network_Packet_Object_xsd.tmp#NeighborOptionsType_Target_Link_Addr Network_Packet_Object_xsd.tmp#NeighborOptionsType
Type PacketObj:NeighborOptionsType
Children PacketObj:Target_Link_Addr
Source
 
<xs:element name="Options" type="PacketObj:NeighborOptionsType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Neighbor Advertisement messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NeighborOptionsType / PacketObj:Target_Link_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
Diagram
Type PacketObj:NDPLinkAddrType
Children PacketObj:Length, PacketObj:Link_Layer_MAC_Addr
Source
Element PacketObj:NDPType / PacketObj:Redirect
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Routers send Redirect packets to inform a host of a better first-hop node on the path to a destination. Hosts can be redirected to a better first-hop router but can also be informed by a redirect that the destination is in fact a neighbor. The latter is accomplished by setting the ICMP Target Address equal to the ICMP Destination Address (type=137; code=0).
Diagram
Diagram Network_Packet_Object_xsd.tmp#RedirectType_Target_IPv6_Addr Network_Packet_Object_xsd.tmp#RedirectType_Dest_IPv6_Addr Network_Packet_Object_xsd.tmp#RedirectType_Options Network_Packet_Object_xsd.tmp#RedirectType
Type PacketObj:RedirectType
Children PacketObj:Dest_IPv6_Addr, PacketObj:Options, PacketObj:Target_IPv6_Addr
Source
 
<xs:element name="Redirect" type="PacketObj:RedirectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Routers send Redirect packets to inform a host of a better first-hop node on the path to a destination. Hosts can be redirected to a better first-hop router but can also be informed by a redirect that the destination is in fact a neighbor. The latter is accomplished by setting the ICMP Target Address equal to the ICMP Destination Address (type=137; code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RedirectType / PacketObj:Target_IPv6_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
An IP address that is a better first hop to use for the ICMP Destination Address.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Target_IPv6_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>An IP address that is a better first hop to use for the ICMP Destination Address.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RedirectType / PacketObj:Dest_IPv6_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The IP address of the destination that is redirected to the target.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Dest_IPv6_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The IP address of the destination that is redirected to the target.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RedirectType / PacketObj:Options
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Redirect messages include zero or more options, some of which may appear multiple times in the same message.
Diagram
Diagram Network_Packet_Object_xsd.tmp#RedirectOptionsType_Target_Link_Addr Network_Packet_Object_xsd.tmp#RedirectOptionsType_Redirected_Header Network_Packet_Object_xsd.tmp#RedirectOptionsType
Type PacketObj:RedirectOptionsType
Children PacketObj:Redirected_Header, PacketObj:Target_Link_Addr
Source
 
<xs:element name="Options" type="PacketObj:RedirectOptionsType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Redirect messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RedirectOptionsType / PacketObj:Target_Link_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
Diagram
Type PacketObj:NDPLinkAddrType
Children PacketObj:Length, PacketObj:Link_Layer_MAC_Addr
Source
Element PacketObj:RedirectOptionsType / PacketObj:Redirected_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
As much as possible of the IP packet that triggered the sending of the Redirect message without making the redirect packet exceed the minimum MTU specified in the IPv6 protocol.
Diagram
Diagram Network_Packet_Object_xsd.tmp#NDPRedirectedHeaderType_Length Network_Packet_Object_xsd.tmp#NDPRedirectedHeaderType_IPHeader_And_Data Network_Packet_Object_xsd.tmp#NDPRedirectedHeaderType
Type PacketObj:NDPRedirectedHeaderType
Children PacketObj:IPHeader_And_Data, PacketObj:Length
Source
 
<xs:element name="Redirected_Header" type="PacketObj:NDPRedirectedHeaderType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>As much as possible of the IP packet that triggered the sending of the Redirect message without making the redirect packet exceed the minimum MTU specified in the IPv6 protocol.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NDPRedirectedHeaderType / PacketObj:Length
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The length of the option (including the type and length fields) in units of 8 octets.
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The length of the option (including the type and length fields) in units of 8 octets.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NDPRedirectedHeaderType / PacketObj:IPHeader_And_Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
As much as possible of the IP packet that triggered the sending of the redirect without making redirect packet larger than MTU.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="IPHeader_And_Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>As much as possible of the IP packet that triggered the sending of the redirect without making redirect packet larger than MTU.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NetworkPacketObjectType / PacketObj:Internet_Layer
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Internet layer characterizes information about the network layer of this Network Packet. The network layer is one layer from the 7-layer OSI Model.
Diagram
Diagram Network_Packet_Object_xsd.tmp#InternetLayerType_IPv4 Network_Packet_Object_xsd.tmp#InternetLayerType_ICMPv4 Network_Packet_Object_xsd.tmp#InternetLayerType_IPv6 Network_Packet_Object_xsd.tmp#InternetLayerType_ICMPv6 Network_Packet_Object_xsd.tmp#InternetLayerType
Type PacketObj:InternetLayerType
Children PacketObj:ICMPv4, PacketObj:ICMPv6, PacketObj:IPv4, PacketObj:IPv6
Source
 
<xs:element name="Internet_Layer" type="PacketObj:InternetLayerType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Internet layer characterizes information about the network layer of this Network Packet. The network layer is one layer from the 7-layer OSI Model.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:InternetLayerType / PacketObj:IPv4
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Internet Protocol version 4 (IPv4) is a connectionless protocol for use on packet-switched link layer networks (e.g., Ethernet).
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4PacketType_IPv4_Header Network_Packet_Object_xsd.tmp#IPv4PacketType_Data Network_Packet_Object_xsd.tmp#IPv4PacketType
Type PacketObj:IPv4PacketType
Children PacketObj:Data, PacketObj:IPv4_Header
Source
 
<xs:element name="IPv4" type="PacketObj:IPv4PacketType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Internet Protocol version 4 (IPv4) is a connectionless protocol for use on packet-switched link layer networks (e.g., Ethernet).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4PacketType / PacketObj:IPv4_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The IPv4 header provides addressing, and internet modules use fields in the header to fragment and reassemble internet datagrams when necessary for transmission through small packet networks.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4HeaderType_IP_Version Network_Packet_Object_xsd.tmp#IPv4HeaderType_Header_Length Network_Packet_Object_xsd.tmp#IPv4HeaderType_DSCP Network_Packet_Object_xsd.tmp#IPv4HeaderType_ECN Network_Packet_Object_xsd.tmp#IPv4HeaderType_Total_Length Network_Packet_Object_xsd.tmp#IPv4HeaderType_Identification Network_Packet_Object_xsd.tmp#IPv4HeaderType_Flags Network_Packet_Object_xsd.tmp#IPv4HeaderType_Fragment_Offset Network_Packet_Object_xsd.tmp#IPv4HeaderType_TTL Network_Packet_Object_xsd.tmp#IPv4HeaderType_Protocol Network_Packet_Object_xsd.tmp#IPv4HeaderType_Checksum Network_Packet_Object_xsd.tmp#IPv4HeaderType_Src_IPv4_Addr Network_Packet_Object_xsd.tmp#IPv4HeaderType_Dest_IPv4_Addr Network_Packet_Object_xsd.tmp#IPv4HeaderType_Option Network_Packet_Object_xsd.tmp#IPv4HeaderType
Type PacketObj:IPv4HeaderType
Children PacketObj:Checksum, PacketObj:DSCP, PacketObj:Dest_IPv4_Addr, PacketObj:ECN, PacketObj:Flags, PacketObj:Fragment_Offset, PacketObj:Header_Length, PacketObj:IP_Version, PacketObj:Identification, PacketObj:Option, PacketObj:Protocol, PacketObj:Src_IPv4_Addr, PacketObj:TTL, PacketObj:Total_Length
Source
 
<xs:element name="IPv4_Header" type="PacketObj:IPv4HeaderType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The IPv4 header provides addressing, and internet modules use fields in the header to fragment and reassemble internet datagrams when necessary for transmission through small packet networks.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4HeaderType / PacketObj:IP_Version
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The version field indicates the format of the internet header. For IP v4, the version is 4.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPVersionType_datatype Network_Packet_Object_xsd.tmp#IPVersionType
Type PacketObj:IPVersionType
Type hierarchy
Source
 
<xs:element name="IP_Version" type="PacketObj:IPVersionType" fixed="IPv4(4)" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The version field indicates the format of the internet header. For IP v4, the version is 4.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4HeaderType / PacketObj:Header_Length
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Internet Header Length specifies the length of IP packet header in 32 bit words. Min value = 5.
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Header_Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The Internet Header Length specifies the length of IP packet header in 32 bit words. Min value = 5.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4HeaderType / PacketObj:DSCP
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Originally defined as the Type of Service field, the Differentiated Services Code Point (DSCP) field is now defined by RFC 2474 for Differentiated services (DiffServ). New technologies are emerging that require real-time data streaming and therefore make use of the DSCP field. An example is Voice over IP (VoIP), which is used for interactive data voice exchange (http://en.wikipedia.org/wiki/IPv4).
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="DSCP" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Originally defined as the Type of Service field, the Differentiated Services Code Point (DSCP) field is now defined by RFC 2474 for Differentiated services (DiffServ). New technologies are emerging that require real-time data streaming and therefore make use of the DSCP field. An example is Voice over IP (VoIP), which is used for interactive data voice exchange (http://en.wikipedia.org/wiki/IPv4).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4HeaderType / PacketObj:ECN
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Explicit Congestion Notification: This field is defined in RFC 3168 and allows end-to-end notification of network congestion without dropping packets. ECN is an optional feature that is only used when both endpoints support it and are willing to use it. It is only effective when supported by the underlying network. (http://en.wikipedia.org/wiki/IPv4).
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="ECN" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Explicit Congestion Notification: This field is defined in RFC 3168 and allows end-to-end notification of network congestion without dropping packets. ECN is an optional feature that is only used when both endpoints support it and are willing to use it. It is only effective when supported by the underlying network. (http://en.wikipedia.org/wiki/IPv4).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4HeaderType / PacketObj:Total_Length
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This 16-bit field defines the entire datagram size, including header and data, in bytes.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Total_Length" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This 16-bit field defines the entire datagram size, including header and data, in bytes.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4HeaderType / PacketObj:Identification
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Identification field is primarily used for uniquely identifying fragments of an original IP datagram. (http://en.wikipedia.org/wiki/IPv4).
Diagram
Diagram
Type PositiveIntegerObjectPropertyType
Source
 
<xs:element name="Identification" type="cyboxCommon:PositiveIntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The Identification field is primarily used for uniquely identifying fragments of an original IP datagram. (http://en.wikipedia.org/wiki/IPv4).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4HeaderType / PacketObj:Flags
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This is a three-bit field used to control or identify fragments. An field has been defined for each bit with associated enumerated types.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4FlagsType_Reserved Network_Packet_Object_xsd.tmp#IPv4FlagsType_Do_Not_Fragment Network_Packet_Object_xsd.tmp#IPv4FlagsType_More_Fragments Network_Packet_Object_xsd.tmp#IPv4FlagsType
Type PacketObj:IPv4FlagsType
Children PacketObj:Do_Not_Fragment, PacketObj:More_Fragments, PacketObj:Reserved
Source
 
<xs:element name="Flags" type="PacketObj:IPv4FlagsType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This is a three-bit field used to control or identify fragments. An field has been defined for each bit with associated enumerated types.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4FlagsType / PacketObj:Reserved
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Bit 0: This bit value (0) is reserved and must be zero.
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Reserved" type="cyboxCommon:IntegerObjectPropertyType" fixed="0" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Bit 0: This bit value (0) is reserved and must be zero.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4FlagsType / PacketObj:Do_Not_Fragment
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Bit 1: This is the "don't fragment" bit. Values are specified in the DoNotFragmentType.
Diagram
Diagram Network_Packet_Object_xsd.tmp#DoNotFragmentType_datatype Network_Packet_Object_xsd.tmp#DoNotFragmentType
Type PacketObj:DoNotFragmentType
Type hierarchy
Source
 
<xs:element name="Do_Not_Fragment" type="PacketObj:DoNotFragmentType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Bit 1: This is the "don't fragment" bit. Values are specified in the DoNotFragmentType.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4FlagsType / PacketObj:More_Fragments
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Bit 2: This is the "more fragments" bit. Values are specified in the MoreFragmentsType.
Diagram
Diagram Network_Packet_Object_xsd.tmp#MoreFragmentsType_datatype Network_Packet_Object_xsd.tmp#MoreFragmentsType
Type PacketObj:MoreFragmentsType
Type hierarchy
Source
 
<xs:element name="More_Fragments" type="PacketObj:MoreFragmentsType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Bit 2: This is the "more fragments" bit. Values are specified in the MoreFragmentsType.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4HeaderType / PacketObj:Fragment_Offset
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The fragment offset field is 13 bits long and specifies the offset of a particular fragment relative to the beginning of the original unfragmented IP datagram. http://en.wikipedia.org/wiki/IPv4.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Fragment_Offset" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The fragment offset field is 13 bits long and specifies the offset of a particular fragment relative to the beginning of the original unfragmented IP datagram. http://en.wikipedia.org/wiki/IPv4.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4HeaderType / PacketObj:TTL
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This 8-bit field helps prevent datagrams from persisting on an internet (it limits a datagram's lifetime).
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="TTL" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This 8-bit field helps prevent datagrams from persisting on an internet (it limits a datagram's lifetime).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4HeaderType / PacketObj:Protocol
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This field defines the protocol used in the data portion of the IP datagram. The type of this field is an enumerated list of IP protocol numbers as maintained by the Internet Assigned Numbers Authority.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType_datatype Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType
Type PacketObj:IANAAssignedIPNumbersType
Type hierarchy
Source
 
<xs:element name="Protocol" type="PacketObj:IANAAssignedIPNumbersType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field defines the protocol used in the data portion of the IP datagram. The type of this field is an enumerated list of IP protocol numbers as maintained by the Internet Assigned Numbers Authority.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4HeaderType / PacketObj:Checksum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This field is a 16-bit checksum used for error-checking of the header.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Checksum" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field is a 16-bit checksum used for error-checking of the header.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4HeaderType / PacketObj:Src_IPv4_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This field is the IPv4 address of the sender of the packet.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Src_IPv4_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field is the IPv4 address of the sender of the packet.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4HeaderType / PacketObj:Dest_IPv4_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This field is the IPv4 address of the receiver of the packet.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Dest_IPv4_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field is the IPv4 address of the receiver of the packet.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4HeaderType / PacketObj:Option
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The IPv4 option field is variable in length with zero or more options. It is not often used. http://en.wikipedia.org/wiki/IPv4.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4OptionType_Copy_Flag Network_Packet_Object_xsd.tmp#IPv4OptionType_Class Network_Packet_Object_xsd.tmp#IPv4OptionType_Option Network_Packet_Object_xsd.tmp#IPv4OptionType
Type PacketObj:IPv4OptionType
Children PacketObj:Class, PacketObj:Copy_Flag, PacketObj:Option
Source
 
<xs:element name="Option" type="PacketObj:IPv4OptionType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>The IPv4 option field is variable in length with zero or more options. It is not often used. http://en.wikipedia.org/wiki/IPv4.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4OptionType / PacketObj:Copy_Flag
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The copied flag indicates that this option is copied into all fragments on fragmentation. 1 bit. They are represented in this field by a string which specifies their value.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4CopyFlagType_datatype Network_Packet_Object_xsd.tmp#IPv4CopyFlagType
Type PacketObj:IPv4CopyFlagType
Type hierarchy
Source
 
<xs:element name="Copy_Flag" type="PacketObj:IPv4CopyFlagType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The copied flag indicates that this option is copied into all fragments on fragmentation. 1 bit. They are represented in this field by a string which specifies their value.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4OptionType / PacketObj:Class
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The option class is represented by 2 bits where 0 = control; 1 = reserved for future use; 2 = debugging and measurement; 3 = reserved for future use. These enumerated values are defined for this field.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4ClassType_datatype Network_Packet_Object_xsd.tmp#IPv4ClassType
Type PacketObj:IPv4ClassType
Type hierarchy
Source
 
<xs:element name="Class" type="PacketObj:IPv4ClassType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The option class is represented by 2 bits where 0 = control; 1 = reserved for future use; 2 = debugging and measurement; 3 = reserved for future use. These enumerated values are defined for this field.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4OptionType / PacketObj:Option
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Internet Protocol has provision for optional header fields identified by an option type. These types are enumerated in the IPv4OptionsType.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4OptionsType_datatype Network_Packet_Object_xsd.tmp#IPv4OptionsType
Type PacketObj:IPv4OptionsType
Type hierarchy
Source
 
<xs:element name="Option" type="PacketObj:IPv4OptionsType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The Internet Protocol has provision for optional header fields identified by an option type. These types are enumerated in the IPv4OptionsType.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv4PacketType / PacketObj:Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The data portion of an IP packet is interpreted based on the value of the Protocol header field. Actual field values will probably be specified in the elements of the different network layers, but we provide a field here to capture any data as necessary.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The data portion of an IP packet is interpreted based on the value of the Protocol header field. Actual field values will probably be specified in the elements of the different network layers, but we provide a field here to capture any data as necessary.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:InternetLayerType / PacketObj:ICMPv4
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ICMP is chiefly used the operating systems of networked computers to send error messages indicating, for example, that a requested service is not available or that a host or router could not be reached (http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol; REF: http://www.networksorcery.com/enp/protocol/icmp.htm).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4PacketType_ICMPv4_Header Network_Packet_Object_xsd.tmp#ICMPv4PacketType_Error_Msg Network_Packet_Object_xsd.tmp#ICMPv4PacketType_Info_Msg Network_Packet_Object_xsd.tmp#ICMPv4PacketType_Traceroute Network_Packet_Object_xsd.tmp#ICMPv4PacketType
Type PacketObj:ICMPv4PacketType
Children PacketObj:Error_Msg, PacketObj:ICMPv4_Header, PacketObj:Info_Msg, PacketObj:Traceroute
Source
 
<xs:element name="ICMPv4" type="PacketObj:ICMPv4PacketType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>ICMP is chiefly used the operating systems of networked computers to send error messages indicating, for example, that a requested service is not available or that a host or router could not be reached (http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol; REF: http://www.networksorcery.com/enp/protocol/icmp.htm).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4PacketType / PacketObj:ICMPv4_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Actual header bytes are captured here. The message content of each type/code pair is also defined as part of the larger, complex "ICMPv4PacketType" type as either an error message, an informational message, or a traceroute message. The meaning of the type and code bytes is made explicit in the elements corresponding to each message type.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4HeaderType_Type Network_Packet_Object_xsd.tmp#ICMPv4HeaderType_Code Network_Packet_Object_xsd.tmp#ICMPv4HeaderType_Checksum Network_Packet_Object_xsd.tmp#ICMPv4HeaderType
Type PacketObj:ICMPv4HeaderType
Children PacketObj:Checksum, PacketObj:Code, PacketObj:Type
Source
 
<xs:element name="ICMPv4_Header" type="PacketObj:ICMPv4HeaderType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Actual header bytes are captured here. The message content of each type/code pair is also defined as part of the larger, complex "ICMPv4PacketType" type as either an error message, an informational message, or a traceroute message. The meaning of the type and code bytes is made explicit in the elements corresponding to each message type.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4HeaderType / PacketObj:Type
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ICMP Type byte specifies the format of the ICMP message.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Type" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>ICMP Type byte specifies the format of the ICMP message.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4HeaderType / PacketObj:Code
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ICMP Code byte further qualifies the ICMP message.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Code" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>ICMP Code byte further qualifies the ICMP message.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4HeaderType / PacketObj:Checksum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ICMP Checksum (16 bits) covers the ICMP message.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Checksum" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>ICMP Checksum (16 bits) covers the ICMP message.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4PacketType / PacketObj:Error_Msg
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
For ICMP error messages, boolean values are used in this field to explicitly interpret the type and code bytes appearing in the ICMP header. Additional fields and message content are also defined here.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageType_Destination_Unreachable Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageType_Source_Quench Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageType_Redirect_Message Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageType_Time_Exceeded Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageType_Error_Msg_Content Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageType
Type PacketObj:ICMPv4ErrorMessageType
Children PacketObj:Destination_Unreachable, PacketObj:Error_Msg_Content, PacketObj:Redirect_Message, PacketObj:Source_Quench, PacketObj:Time_Exceeded
Source
 
<xs:element name="Error_Msg" type="PacketObj:ICMPv4ErrorMessageType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>For ICMP error messages, boolean values are used in this field to explicitly interpret the type and code bytes appearing in the ICMP header. Additional fields and message content are also defined here.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4ErrorMessageType / PacketObj:Destination_Unreachable
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
A destination unreachable message is an ICMP message which is generated by the host or its inbound gateway to inform the client that the destination is unreachable for some reason (http://en.wikipedia.org/wiki/ICMP_Destination_Unreachable).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Destination_Network_Unreachable Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Destination_Host_Unreachable Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Destination_Protocol_Unreachable Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Destination_Port_Unreachable Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Fragmentation_Required Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Source_Route_Failed Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Destination_Network_Unknown Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Destination_Host_Unknown Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Source_Host_Isolated Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Network_Administratively_Prohibited Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Host_Administratively_Prohibited Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Network_Unreachable_For_TOS Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Host_Unreachable_For_TOS Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Communication_Administratively_Prohibited Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Host_Precedence_Violation Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Precedence_Cutoff_In_Effect Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType
Type PacketObj:ICMPv4DestinationUnreachableType
Children PacketObj:Communication_Administratively_Prohibited, PacketObj:Destination_Host_Unknown, PacketObj:Destination_Host_Unreachable, PacketObj:Destination_Network_Unknown, PacketObj:Destination_Network_Unreachable, PacketObj:Destination_Port_Unreachable, PacketObj:Destination_Protocol_Unreachable, PacketObj:Fragmentation_Required, PacketObj:Host_Administratively_Prohibited, PacketObj:Host_Precedence_Violation, PacketObj:Host_Unreachable_For_TOS, PacketObj:Network_Administratively_Prohibited, PacketObj:Network_Unreachable_For_TOS, PacketObj:Precedence_Cutoff_In_Effect, PacketObj:Source_Host_Isolated, PacketObj:Source_Route_Failed
Source
 
<xs:element name="Destination_Unreachable" type="PacketObj:ICMPv4DestinationUnreachableType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>A destination unreachable message is an ICMP message which is generated by the host or its inbound gateway to inform the client that the destination is unreachable for some reason (http://en.wikipedia.org/wiki/ICMP_Destination_Unreachable).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Destination_Network_Unreachable
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; destination network unreachable (code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Destination_Network_Unreachable" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; destination network unreachable (code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Destination_Host_Unreachable
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; destination host unreachable (code=1).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Destination_Host_Unreachable" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; destination host unreachable (code=1).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Destination_Protocol_Unreachable
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; destination protocol unreachable (code=2).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Destination_Protocol_Unreachable" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; destination protocol unreachable (code=2).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Destination_Port_Unreachable
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; destination port unreachable (code=3).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Destination_Port_Unreachable" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; destination port unreachable (code=3).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Fragmentation_Required
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; fragmentation required (code=4). This field has an additional field (Next-Hop MTU), as well as a boolean value indicating this subtype.
Diagram
Diagram Network_Packet_Object_xsd.tmp#FragmentationRequiredType_Fragmentation_Required Network_Packet_Object_xsd.tmp#FragmentationRequiredType_Next_Hop_MTU Network_Packet_Object_xsd.tmp#FragmentationRequiredType
Type PacketObj:FragmentationRequiredType
Children PacketObj:Fragmentation_Required, PacketObj:Next_Hop_MTU
Source
 
<xs:element name="Fragmentation_Required" type="PacketObj:FragmentationRequiredType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; fragmentation required (code=4). This field has an additional field (Next-Hop MTU), as well as a boolean value indicating this subtype.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:FragmentationRequiredType / PacketObj:Fragmentation_Required
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Indicates that the subtype of the destination unreachable ICMP message is "fragmentation required".
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Fragmentation_Required" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Indicates that the subtype of the destination unreachable ICMP message is "fragmentation required".</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:FragmentationRequiredType / PacketObj:Next_Hop_MTU
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Next-Hop MTU field contains the MTU of the next-hop network is a code 4 error (fragmentation required) occurs.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Next_Hop_MTU" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The Next-Hop MTU field contains the MTU of the next-hop network is a code 4 error (fragmentation required) occurs.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Source_Route_Failed
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; source route failed (code=5).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Source_Route_Failed" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; source route failed (code=5).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Destination_Network_Unknown
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; destination network unknown (code=6).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Destination_Network_Unknown" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; destination network unknown (code=6).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Destination_Host_Unknown
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; destination host unknown (code=7).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Destination_Host_Unknown" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; destination host unknown (code=7).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Source_Host_Isolated
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; source host isolated (code=8).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Source_Host_Isolated" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; source host isolated (code=8).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Network_Administratively_Prohibited
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; host administratively prohibited (code=9).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Network_Administratively_Prohibited" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; host administratively prohibited (code=9).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Host_Administratively_Prohibited
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; host administratively prohibited (code=10).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Host_Administratively_Prohibited" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; host administratively prohibited (code=10).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Network_Unreachable_For_TOS
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; network unreachable for TOS (code=11).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Network_Unreachable_For_TOS" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; network unreachable for TOS (code=11).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Host_Unreachable_For_TOS
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; host unreachable for TOS (code=12).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Host_Unreachable_For_TOS" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; host unreachable for TOS (code=12).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Communication_Administratively_Prohibited
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; communication administratively prohibited (code=13).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Communication_Administratively_Prohibited" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; communication administratively prohibited (code=13).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Host_Precedence_Violation
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; host precedence violation (code=14).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Host_Precedence_Violation" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; host precedence violation (code=14).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4DestinationUnreachableType / PacketObj:Precedence_Cutoff_In_Effect
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 16 different subtypes of a destination unreachable ICMP message; precedence cutoff in effect (code=15).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Precedence_Cutoff_In_Effect" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; precedence cutoff in effect (code=15).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4ErrorMessageType / PacketObj:Source_Quench
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
A source quench message is an ICMP message that requests that the sender decrease the rate of messages sent to a router or host. This message may be generated if a router or host does not have sufficient buffer space to process the request or may occur if the router or host buffer is approaching its limit (http://en.wikipedia.org/wiki/ICMP_Source_Quench).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4SourceQuenchType_Source_Quench Network_Packet_Object_xsd.tmp#ICMPv4SourceQuenchType
Type PacketObj:ICMPv4SourceQuenchType
Children PacketObj:Source_Quench
Source
 
<xs:element name="Source_Quench" type="PacketObj:ICMPv4SourceQuenchType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>A source quench message is an ICMP message that requests that the sender decrease the rate of messages sent to a router or host. This message may be generated if a router or host does not have sufficient buffer space to process the request or may occur if the router or host buffer is approaching its limit (http://en.wikipedia.org/wiki/ICMP_Source_Quench).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4SourceQuenchType / PacketObj:Source_Quench
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Source quench is the only subtype (code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Source_Quench" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Source quench is the only subtype (code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4ErrorMessageType / PacketObj:Redirect_Message
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
A redirect message is used to send data packets on an alternative route. This ICMP redirect message informs a host to update its routing information.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4RedirectMessageType_Network_Redirect Network_Packet_Object_xsd.tmp#ICMPv4RedirectMessageType_Host_Redirect Network_Packet_Object_xsd.tmp#ICMPv4RedirectMessageType_ToS_Network_Redirect Network_Packet_Object_xsd.tmp#ICMPv4RedirectMessageType_ToS_Host_Redirect Network_Packet_Object_xsd.tmp#ICMPv4RedirectMessageType_IP_Address Network_Packet_Object_xsd.tmp#ICMPv4RedirectMessageType
Type PacketObj:ICMPv4RedirectMessageType
Children PacketObj:Host_Redirect, PacketObj:IP_Address, PacketObj:Network_Redirect, PacketObj:ToS_Host_Redirect, PacketObj:ToS_Network_Redirect
Source
 
<xs:element name="Redirect_Message" type="PacketObj:ICMPv4RedirectMessageType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>A redirect message is used to send data packets on an alternative route. This ICMP redirect message informs a host to update its routing information.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4RedirectMessageType / PacketObj:Network_Redirect
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 4 different subtypes of a redirect ICMP message; redirect datagram for the network (code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Network_Redirect" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 4 different subtypes of a redirect ICMP message; redirect datagram for the network (code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4RedirectMessageType / PacketObj:Host_Redirect
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 4 different subtypes of a redirect ICMP message; redirect datagram for the host (code=1).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Host_Redirect" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 4 different subtypes of a redirect ICMP message; redirect datagram for the host (code=1).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4RedirectMessageType / PacketObj:ToS_Network_Redirect
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 4 different subtypes of a redirect ICMP message; redirect datagram for the TOS and network (code=2).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="ToS_Network_Redirect" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 4 different subtypes of a redirect ICMP message; redirect datagram for the TOS and network (code=2).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4RedirectMessageType / PacketObj:ToS_Host_Redirect
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of 4 different subtypes of a redirect ICMP message; redirect datagram for the TOS and host (code=3).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="ToS_Host_Redirect" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of 4 different subtypes of a redirect ICMP message; redirect datagram for the TOS and host (code=3).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4RedirectMessageType / PacketObj:IP_Address
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The IP address is the 32-bit address of the gateway to which the redirection should be sent.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="IP_Address" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The IP address is the 32-bit address of the gateway to which the redirection should be sent.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4ErrorMessageType / PacketObj:Time_Exceeded
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
An ICMP time exceeded message is generated by a gateway to inform the source of a datagram that the datagram has been discarded due to the time to live field reaching zero. A time exceeded message may also be sent by a host if it fails to reassemble a fragmented datagram within its time limit (http://en.wikipedia.org/wiki/ICMP_Time_Exceeded).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4TimeExceededType_TTL_Exceeded_In_Transit Network_Packet_Object_xsd.tmp#ICMPv4TimeExceededType_Frag_Reassembly_Time_Exceeded Network_Packet_Object_xsd.tmp#ICMPv4TimeExceededType
Type PacketObj:ICMPv4TimeExceededType
Children PacketObj:Frag_Reassembly_Time_Exceeded, PacketObj:TTL_Exceeded_In_Transit
Source
 
<xs:element name="Time_Exceeded" type="PacketObj:ICMPv4TimeExceededType" form="qualified" minOccurs="0">
  <xs:annotation>
    <xs:documentation>An ICMP time exceeded message is generated by a gateway to inform the source of a datagram that the datagram has been discarded due to the time to live field reaching zero. A time exceeded message may also be sent by a host if it fails to reassemble a fragmented datagram within its time limit (http://en.wikipedia.org/wiki/ICMP_Time_Exceeded).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4TimeExceededType / PacketObj:TTL_Exceeded_In_Transit
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
specifies that the time-to-live was exceeded in transit (code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="TTL_Exceeded_In_Transit" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>specifies that the time-to-live was exceeded in transit (code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4TimeExceededType / PacketObj:Frag_Reassembly_Time_Exceeded
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
specifies that the fragment reassembly time was exceeded (code=1).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Frag_Reassembly_Time_Exceeded" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>specifies that the fragment reassembly time was exceeded (code=1).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4ErrorMessageType / PacketObj:Error_Msg_Content
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Message content common to all ICMP error messages are defined here. Fields that are specific to individual messages are defined separately under each message type.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageContentType_IP_Header Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageContentType_First_Eight_Bytes Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageContentType
Type PacketObj:ICMPv4ErrorMessageContentType
Children PacketObj:First_Eight_Bytes, PacketObj:IP_Header
Source
 
<xs:element name="Error_Msg_Content" type="PacketObj:ICMPv4ErrorMessageContentType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Message content common to all ICMP error messages are defined here. Fields that are specific to individual messages are defined separately under each message type.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4ErrorMessageContentType / PacketObj:IP_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
IP header from the original datagram.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4HeaderType_IP_Version Network_Packet_Object_xsd.tmp#IPv4HeaderType_Header_Length Network_Packet_Object_xsd.tmp#IPv4HeaderType_DSCP Network_Packet_Object_xsd.tmp#IPv4HeaderType_ECN Network_Packet_Object_xsd.tmp#IPv4HeaderType_Total_Length Network_Packet_Object_xsd.tmp#IPv4HeaderType_Identification Network_Packet_Object_xsd.tmp#IPv4HeaderType_Flags Network_Packet_Object_xsd.tmp#IPv4HeaderType_Fragment_Offset Network_Packet_Object_xsd.tmp#IPv4HeaderType_TTL Network_Packet_Object_xsd.tmp#IPv4HeaderType_Protocol Network_Packet_Object_xsd.tmp#IPv4HeaderType_Checksum Network_Packet_Object_xsd.tmp#IPv4HeaderType_Src_IPv4_Addr Network_Packet_Object_xsd.tmp#IPv4HeaderType_Dest_IPv4_Addr Network_Packet_Object_xsd.tmp#IPv4HeaderType_Option Network_Packet_Object_xsd.tmp#IPv4HeaderType
Type PacketObj:IPv4HeaderType
Children PacketObj:Checksum, PacketObj:DSCP, PacketObj:Dest_IPv4_Addr, PacketObj:ECN, PacketObj:Flags, PacketObj:Fragment_Offset, PacketObj:Header_Length, PacketObj:IP_Version, PacketObj:Identification, PacketObj:Option, PacketObj:Protocol, PacketObj:Src_IPv4_Addr, PacketObj:TTL, PacketObj:Total_Length
Source
 
<xs:element name="IP_Header" type="PacketObj:IPv4HeaderType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>IP header from the original datagram.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4ErrorMessageContentType / PacketObj:First_Eight_Bytes
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
First 8 bytes of the original datagram's data.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="First_Eight_Bytes" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>First 8 bytes of the original datagram's data.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4PacketType / PacketObj:Info_Msg
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
For ICMP informational messages, boolean values are used in this field to explicitly interpret the type and code bytes appearing in the ICMP header. Additional fields and message content are also defined here.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType_Echo_Reply Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType_Echo_Request Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType_Timestamp_Request Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType_Timestamp_Reply Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType_Address_Mask_Request Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType_Address_Mask_Reply Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType_Info_Msg_Content Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType
Type PacketObj:ICMPv4InfoMessageType
Children PacketObj:Address_Mask_Reply, PacketObj:Address_Mask_Request, PacketObj:Echo_Reply, PacketObj:Echo_Request, PacketObj:Info_Msg_Content, PacketObj:Timestamp_Reply, PacketObj:Timestamp_Request
Source
 
<xs:element name="Info_Msg" type="PacketObj:ICMPv4InfoMessageType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>For ICMP informational messages, boolean values are used in this field to explicitly interpret the type and code bytes appearing in the ICMP header. Additional fields and message content are also defined here.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4InfoMessageType / PacketObj:Echo_Reply
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Echo reply/request messages are also known as "ping". The Info_Message_Content field contains an identifier and sequence number which together form the "quench" for echo reply and echo request. Fields specific to an echo reply message are given as elements to this echo reply field (type=0).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4EchoReplyType_Echo_Reply Network_Packet_Object_xsd.tmp#ICMPv4EchoReplyType_Data Network_Packet_Object_xsd.tmp#ICMPv4EchoReplyType
Type PacketObj:ICMPv4EchoReplyType
Children PacketObj:Data, PacketObj:Echo_Reply
Source
 
<xs:element name="Echo_Reply" type="PacketObj:ICMPv4EchoReplyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Echo reply/request messages are also known as "ping". The Info_Message_Content field contains an identifier and sequence number which together form the "quench" for echo reply and echo request. Fields specific to an echo reply message are given as elements to this echo reply field (type=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4EchoReplyType / PacketObj:Echo_Reply
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Echo reply is the only subtype (code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Echo_Reply" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Echo reply is the only subtype (code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4EchoReplyType / PacketObj:Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This data is optional and is used for the different kind of answers given with an ICMP Echo Reply message. Can be arbitrary length (but less than the MTU of the network).
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This data is optional and is used for the different kind of answers given with an ICMP Echo Reply message. Can be arbitrary length (but less than the MTU of the network).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4InfoMessageType / PacketObj:Echo_Request
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Echo reply/request messages are also known as "ping". The Info_Message_Content field contains an identifier and sequence number which together form the "quench" for echo reply and echo request. Fields specific to an echo request message are given as elements to this echo request field (type=8).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4EchoRequestType_Echo_Request Network_Packet_Object_xsd.tmp#ICMPv4EchoRequestType_Data Network_Packet_Object_xsd.tmp#ICMPv4EchoRequestType
Type PacketObj:ICMPv4EchoRequestType
Children PacketObj:Data, PacketObj:Echo_Request
Source
 
<xs:element name="Echo_Request" type="PacketObj:ICMPv4EchoRequestType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Echo reply/request messages are also known as "ping". The Info_Message_Content field contains an identifier and sequence number which together form the "quench" for echo reply and echo request. Fields specific to an echo request message are given as elements to this echo request field (type=8).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4EchoRequestType / PacketObj:Echo_Request
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Echo request is the only subtype (code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Echo_Request" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Echo request is the only subtype (code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4EchoRequestType / PacketObj:Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This data is optional and is used for the different kind of answers given with an ICMP Echo Request message. Can be arbitrary length (but less than the MTU of the network).
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This data is optional and is used for the different kind of answers given with an ICMP Echo Request message. Can be arbitrary length (but less than the MTU of the network).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4InfoMessageType / PacketObj:Timestamp_Request
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
A timestamp request is an ICMP informational message used for time synchronization.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4TimestampRequestType_Timestamp Network_Packet_Object_xsd.tmp#ICMPv4TimestampRequestType_Originate_Timestamp Network_Packet_Object_xsd.tmp#ICMPv4TimestampRequestType
Type PacketObj:ICMPv4TimestampRequestType
Children PacketObj:Originate_Timestamp, PacketObj:Timestamp
Source
 
<xs:element name="Timestamp_Request" type="PacketObj:ICMPv4TimestampRequestType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>A timestamp request is an ICMP informational message used for time synchronization.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4TimestampRequestType / PacketObj:Timestamp
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This is the only subtype of a timestamp request message (code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Timestamp" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This is the only subtype of a timestamp request message (code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4TimestampRequestType / PacketObj:Originate_Timestamp
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
32-bits; number of ms since midnight UT. The originate timestamp is the time the sender last touched the message before sending it. If the time is not available in milliseconds 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.
Diagram
Diagram
Type UnsignedIntegerObjectPropertyType
Source
 
<xs:element name="Originate_Timestamp" type="cyboxCommon:UnsignedIntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>32-bits; number of ms since midnight UT. The originate timestamp is the time the sender last touched the message before sending it. If the time is not available in milliseconds 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.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4InfoMessageType / PacketObj:Timestamp_Reply
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
A timestamp reply is an informational ICMP message which replies to a timestamp request message.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4TimestampReplyType_Timestamp_Reply Network_Packet_Object_xsd.tmp#ICMPv4TimestampReplyType_Originate_Timestamp Network_Packet_Object_xsd.tmp#ICMPv4TimestampReplyType_Receive_Timestamp Network_Packet_Object_xsd.tmp#ICMPv4TimestampReplyType_Transmit_Timestamp Network_Packet_Object_xsd.tmp#ICMPv4TimestampReplyType
Type PacketObj:ICMPv4TimestampReplyType
Children PacketObj:Originate_Timestamp, PacketObj:Receive_Timestamp, PacketObj:Timestamp_Reply, PacketObj:Transmit_Timestamp
Source
 
<xs:element name="Timestamp_Reply" type="PacketObj:ICMPv4TimestampReplyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>A timestamp reply is an informational ICMP message which replies to a timestamp request message.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4TimestampReplyType / PacketObj:Timestamp_Reply
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This is the only subtype of a timestamp reply message (code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Timestamp_Reply" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This is the only subtype of a timestamp reply message (code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4TimestampReplyType / PacketObj:Originate_Timestamp
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The originate timestamp is the time the sender last touched the message before sending it. If the time is not available in milliseconds 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.
Diagram
Diagram
Type UnsignedIntegerObjectPropertyType
Source
 
<xs:element name="Originate_Timestamp" type="cyboxCommon:UnsignedIntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The originate timestamp is the time the sender last touched the message before sending it. If the time is not available in milliseconds 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.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4TimestampReplyType / PacketObj:Receive_Timestamp
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The receive timestamp is the time the echoer first touched the message on receipt. If the time is not available in milliseconds 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.
Diagram
Diagram
Type UnsignedIntegerObjectPropertyType
Source
 
<xs:element name="Receive_Timestamp" type="cyboxCommon:UnsignedIntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The receive timestamp is the time the echoer first touched the message on receipt. If the time is not available in milliseconds 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.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4TimestampReplyType / PacketObj:Transmit_Timestamp
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The transmit timestamp is the time the echoer last touched the message on sending it. If the time is not available in milliseconds 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.
Diagram
Diagram
Type UnsignedIntegerObjectPropertyType
Source
 
<xs:element name="Transmit_Timestamp" type="cyboxCommon:UnsignedIntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The transmit timestamp is the time the echoer last touched the message on sending it. If the time is not available in milliseconds 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.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4InfoMessageType / PacketObj:Address_Mask_Request
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
An address mask request is an ICMP informational message (query message) normally sent by a host to a router in order to obtain an appropriate subnet mask (type=17).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4AddressMaskRequestType_Address_Mask_Request Network_Packet_Object_xsd.tmp#ICMPv4AddressMaskRequestType_Address_Mask Network_Packet_Object_xsd.tmp#ICMPv4AddressMaskRequestType
Type PacketObj:ICMPv4AddressMaskRequestType
Children PacketObj:Address_Mask, PacketObj:Address_Mask_Request
Source
 
<xs:element name="Address_Mask_Request" type="PacketObj:ICMPv4AddressMaskRequestType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>An address mask request is an ICMP informational message (query message) normally sent by a host to a router in order to obtain an appropriate subnet mask (type=17).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4AddressMaskRequestType / PacketObj:Address_Mask_Request
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This is the only possible subtype of an address mask request message (code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Address_Mask_Request" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This is the only possible subtype of an address mask request message (code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4AddressMaskRequestType / PacketObj:Address_Mask
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The address mask can be set to 0 in an address mask request message (as opposed to an address mask reply message, in which case it should be set to the subnet mask).
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Address_Mask" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The address mask can be set to 0 in an address mask request message (as opposed to an address mask reply message, in which case it should be set to the subnet mask).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4InfoMessageType / PacketObj:Address_Mask_Reply
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
An address mask reply is an ICMP informational message, used to reply to an address mask request message with an appropriate subnet mask (type=18).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4AddressMaskReplyType_Address_Mask_Reply Network_Packet_Object_xsd.tmp#ICMPv4AddressMaskReplyType_Address_Mask Network_Packet_Object_xsd.tmp#ICMPv4AddressMaskReplyType
Type PacketObj:ICMPv4AddressMaskReplyType
Children PacketObj:Address_Mask, PacketObj:Address_Mask_Reply
Source
 
<xs:element name="Address_Mask_Reply" type="PacketObj:ICMPv4AddressMaskReplyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>An address mask reply is an ICMP informational message, used to reply to an address mask request message with an appropriate subnet mask (type=18).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4AddressMaskReplyType / PacketObj:Address_Mask_Reply
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This is the only possible subtype of an address mask reply message (code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Address_Mask_Reply" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This is the only possible subtype of an address mask reply message (code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4AddressMaskReplyType / PacketObj:Address_Mask
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This address mask field should be set to the subnet mask.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Address_Mask" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This address mask field should be set to the subnet mask.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4InfoMessageType / PacketObj:Info_Msg_Content
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Fields that are common to all ICMP informational messages are defined here. Fields that are specific to individual messages are defined separately under each message type.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageContentType_Identifier Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageContentType_Sequence_Number Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageContentType
Type PacketObj:ICMPv4InfoMessageContentType
Children PacketObj:Identifier, PacketObj:Sequence_Number
Source
 
<xs:element name="Info_Msg_Content" type="PacketObj:ICMPv4InfoMessageContentType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Fields that are common to all ICMP informational messages are defined here. Fields that are specific to individual messages are defined separately under each message type.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4InfoMessageContentType / PacketObj:Identifier
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
16-bit identifier. Combined with the sequence number, called the "quench" for echo reply and echo request.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Identifier" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>16-bit identifier. Combined with the sequence number, called the "quench" for echo reply and echo request.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4InfoMessageContentType / PacketObj:Sequence_Number
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
16-bit sequence number. The identifier and sequence number can be used by the client to match the reply with the request that caused the reply.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Sequence_Number" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>16-bit sequence number. The identifier and sequence number can be used by the client to match the reply with the request that caused the reply.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4PacketType / PacketObj:Traceroute
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
For ICMP traceroute messages (type = 30), specifies related fields and ICMP code value. A boolean value is used to explicitly interpret the code byte appearing in the ICMP header. Additional fields and message content are also defined here.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType_Outbound_Packet_Forward_Success Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType_Outbound_Packet_no_Route Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType_Identifier Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType_Outbound_Hop_Count Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType_Return_Hop_Count Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType_Output_Link_Speed Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType_Output_Link_MTU Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType
Type PacketObj:ICMPv4TracerouteType
Children PacketObj:Identifier, PacketObj:Outbound_Hop_Count, PacketObj:Outbound_Packet_Forward_Success, PacketObj:Outbound_Packet_no_Route, PacketObj:Output_Link_MTU, PacketObj:Output_Link_Speed, PacketObj:Return_Hop_Count
Source
 
<xs:element name="Traceroute" type="PacketObj:ICMPv4TracerouteType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>For ICMP traceroute messages (type = 30), specifies related fields and ICMP code value. A boolean value is used to explicitly interpret the code byte appearing in the ICMP header. Additional fields and message content are also defined here.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4TracerouteType / PacketObj:Outbound_Packet_Forward_Success
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of two possible subtypes for an ICMP traceroute message. This subtype means that the outbound packet was successfully forwarded (code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Outbound_Packet_Forward_Success" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of two possible subtypes for an ICMP traceroute message. This subtype means that the outbound packet was successfully forwarded (code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4TracerouteType / PacketObj:Outbound_Packet_no_Route
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
One of two possible subtypes for an ICMP traceroute message. This one means that there is no route for the outbound packet and the packet was discarded (code=1).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Outbound_Packet_no_Route" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>One of two possible subtypes for an ICMP traceroute message. This one means that there is no route for the outbound packet and the packet was discarded (code=1).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4TracerouteType / PacketObj:Identifier
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
16 bits. The ID number as copied from the ICMP traceroute option of the packet which caused this traceroute message to be sent (not related to the ID number in the IP header). (http://www.networksorcery.com/enp/protocol/icmp/msg30.htm).
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Identifier" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>16 bits. The ID number as copied from the ICMP traceroute option of the packet which caused this traceroute message to be sent (not related to the ID number in the IP header). (http://www.networksorcery.com/enp/protocol/icmp/msg30.htm).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4TracerouteType / PacketObj:Outbound_Hop_Count
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
16 bits. Outbound hop count as copied from the IP traceroute option of the packet which caused this traceroute message to be sent (http://www.networksorcery.com/enp/protocol/icmp/msg30.htm).
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Outbound_Hop_Count" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>16 bits. Outbound hop count as copied from the IP traceroute option of the packet which caused this traceroute message to be sent (http://www.networksorcery.com/enp/protocol/icmp/msg30.htm).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4TracerouteType / PacketObj:Return_Hop_Count
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
16 bits. Return hop count as copied from the IP traceroute options of the packet which caused this traceroute message to be sent. (http://www.networksorcery.com/enp/protocol/icmp/msg30.htm).
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Return_Hop_Count" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>16 bits. Return hop count as copied from the IP traceroute options of the packet which caused this traceroute message to be sent. (http://www.networksorcery.com/enp/protocol/icmp/msg30.htm).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv4TracerouteType / PacketObj:Output_Link_Speed
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
Diagram
Type HexBinaryObjectPropertyType
Source
Element PacketObj:ICMPv4TracerouteType / PacketObj:Output_Link_MTU
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
Diagram
Type HexBinaryObjectPropertyType
Source
Element PacketObj:InternetLayerType / PacketObj:IPv6
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Internet Protocol version 6 (IPv6) is intended to succeed IPv4, and like IPv4 it is a connectionless protocol for use on packet-switched link layer networks.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv6PacketType_IPv6_Header Network_Packet_Object_xsd.tmp#IPv6PacketType_Ext_Headers Network_Packet_Object_xsd.tmp#IPv6PacketType_Data Network_Packet_Object_xsd.tmp#IPv6PacketType
Type PacketObj:IPv6PacketType
Children PacketObj:Data, PacketObj:Ext_Headers, PacketObj:IPv6_Header
Source
 
<xs:element name="IPv6" type="PacketObj:IPv6PacketType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Internet Protocol version 6 (IPv6) is intended to succeed IPv4, and like IPv4 it is a connectionless protocol for use on packet-switched link layer networks.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6PacketType / PacketObj:IPv6_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
IPv6 headers is a simplification of the IPv4 header.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv6HeaderType_IP_Version Network_Packet_Object_xsd.tmp#IPv6HeaderType_Traffic_Class Network_Packet_Object_xsd.tmp#IPv6HeaderType_Flow_Label Network_Packet_Object_xsd.tmp#IPv6HeaderType_Payload_Length Network_Packet_Object_xsd.tmp#IPv6HeaderType_Next_Header Network_Packet_Object_xsd.tmp#IPv6HeaderType_TTL Network_Packet_Object_xsd.tmp#IPv6HeaderType_Src_IPv6_Addr Network_Packet_Object_xsd.tmp#IPv6HeaderType_Dest_IPv6_Addr Network_Packet_Object_xsd.tmp#IPv6HeaderType
Type PacketObj:IPv6HeaderType
Children PacketObj:Dest_IPv6_Addr, PacketObj:Flow_Label, PacketObj:IP_Version, PacketObj:Next_Header, PacketObj:Payload_Length, PacketObj:Src_IPv6_Addr, PacketObj:TTL, PacketObj:Traffic_Class
Source
 
<xs:element name="IPv6_Header" type="PacketObj:IPv6HeaderType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>IPv6 headers is a simplification of the IPv4 header.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6HeaderType / PacketObj:IP_Version
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
4-bit Internet Protocol version number =6.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPVersionType_datatype Network_Packet_Object_xsd.tmp#IPVersionType
Type PacketObj:IPVersionType
Type hierarchy
Source
 
<xs:element name="IP_Version" type="PacketObj:IPVersionType" fixed="IPv6(6)" minOccurs="0">
  <xs:annotation>
    <xs:documentation>4-bit Internet Protocol version number =6.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6HeaderType / PacketObj:Traffic_Class
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
8-bit traffic class field. Available for use by originating nodes and/or forwarding routers to identify and distinguish between different classes or priorities of IPv6 packets. http://tools.ietf.org/html/rfc2460#section-7.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Traffic_Class" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>8-bit traffic class field. Available for use by originating nodes and/or forwarding routers to identify and distinguish between different classes or priorities of IPv6 packets. http://tools.ietf.org/html/rfc2460#section-7.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6HeaderType / PacketObj:Flow_Label
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
20-bit flow label. Used by a source to label sequences of packets for which it requests special handling by the IPv6 routers, such as non-default quality of service. http://tools.ietf.org/html/rfc2460#section-6.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Flow_Label" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>20-bit flow label. Used by a source to label sequences of packets for which it requests special handling by the IPv6 routers, such as non-default quality of service. http://tools.ietf.org/html/rfc2460#section-6.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6HeaderType / PacketObj:Payload_Length
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
16-bit unsigned integer. Length of the IPv6 payload (the rest of the packet following the IPv6 header) in octets. Any extension headers are considered part of the payload.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Payload_Length" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>16-bit unsigned integer. Length of the IPv6 payload (the rest of the packet following the IPv6 header) in octets. Any extension headers are considered part of the payload.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6HeaderType / PacketObj:Next_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
8-bit selector. Identifies the type of header immediately following the IPv6 header. Uses the same values as the IPv4 protocol field.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType_datatype Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType
Type PacketObj:IANAAssignedIPNumbersType
Type hierarchy
Source
 
<xs:element name="Next_Header" type="PacketObj:IANAAssignedIPNumbersType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>8-bit selector. Identifies the type of header immediately following the IPv6 header. Uses the same values as the IPv4 protocol field.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6HeaderType / PacketObj:TTL
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
TTL/hop limit specifies how many times a packet can be forwarded. 8-bit unsigned integer.
Diagram
Diagram
Type PositiveIntegerObjectPropertyType
Source
 
<xs:element name="TTL" type="cyboxCommon:PositiveIntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>TTL/hop limit specifies how many times a packet can be forwarded. 8-bit unsigned integer.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6HeaderType / PacketObj:Src_IPv6_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
128-bit address of the originator of the packet.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Src_IPv6_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>128-bit address of the originator of the packet.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6HeaderType / PacketObj:Dest_IPv6_Addr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
128-bit address of the intended recipient of the packet.
Diagram
Diagram
Type AddressObjectType
Source
 
<xs:element name="Dest_IPv6_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>128-bit address of the intended recipient of the packet.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6PacketType / PacketObj:Ext_Headers
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
In IPv6, optional internet-layer information is encoded in separate headers that may be placed between the IPv6 header and the upper-layer header in a packet. http://tools.ietf.org/html/rfc2460.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv6ExtHeaderType_Hop_by_Hop_Options Network_Packet_Object_xsd.tmp#IPv6ExtHeaderType_Routing Network_Packet_Object_xsd.tmp#IPv6ExtHeaderType_Fragment Network_Packet_Object_xsd.tmp#IPv6ExtHeaderType_Destination_Options Network_Packet_Object_xsd.tmp#IPv6ExtHeaderType_Authentication_Header Network_Packet_Object_xsd.tmp#IPv6ExtHeaderType_Encapsulating_Security_Payload Network_Packet_Object_xsd.tmp#IPv6ExtHeaderType
Type PacketObj:IPv6ExtHeaderType
Children PacketObj:Authentication_Header, PacketObj:Destination_Options, PacketObj:Encapsulating_Security_Payload, PacketObj:Fragment, PacketObj:Hop_by_Hop_Options, PacketObj:Routing
Source
 
<xs:element name="Ext_Headers" type="PacketObj:IPv6ExtHeaderType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>In IPv6, optional internet-layer information is encoded in separate headers that may be placed between the IPv6 header and the upper-layer header in a packet. http://tools.ietf.org/html/rfc2460.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6ExtHeaderType / PacketObj:Hop_by_Hop_Options
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Hop-by-Hop Options header is used to carry optional information that must be examined by every node along a packet's delivery path. It carries a variable number of type-length-value (TLV) encoded options.
Diagram
Diagram Network_Packet_Object_xsd.tmp#HopByHopOptionsType_Next_Header Network_Packet_Object_xsd.tmp#HopByHopOptionsType_Header_Ext_Len Network_Packet_Object_xsd.tmp#HopByHopOptionsType_Option_Data Network_Packet_Object_xsd.tmp#HopByHopOptionsType
Type PacketObj:HopByHopOptionsType
Children PacketObj:Header_Ext_Len, PacketObj:Next_Header, PacketObj:Option_Data
Source
 
<xs:element name="Hop_by_Hop_Options" type="PacketObj:HopByHopOptionsType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The Hop-by-Hop Options header is used to carry optional information that must be examined by every node along a packet's delivery path. It carries a variable number of type-length-value (TLV) encoded options.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:HopByHopOptionsType / PacketObj:Next_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Identifies the type of header immediately following the Hop-by-Hop Options header. Uses the same values as the IPv4 Protocol field.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType_datatype Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType
Type PacketObj:IANAAssignedIPNumbersType
Type hierarchy
Source
 
<xs:element name="Next_Header" type="PacketObj:IANAAssignedIPNumbersType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Identifies the type of header immediately following the Hop-by-Hop Options header. Uses the same values as the IPv4 Protocol field.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:HopByHopOptionsType / PacketObj:Header_Ext_Len
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Length of the Hop-by-Hop Options header in 8-octet units, not including the first 8 octets.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Header_Ext_Len" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Length of the Hop-by-Hop Options header in 8-octet units, not including the first 8 octets.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:HopByHopOptionsType / PacketObj:Option_Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Variable-length field, of length such that the complete Hop-by-Hop Options header is an integer multiple of 8 octets long. Contains one or more type-length-value (TLV)-encoded options.
Diagram
Diagram Network_Packet_Object_xsd.tmp#OptionDataType_Option_Type Network_Packet_Object_xsd.tmp#OptionDataType_Option_Data_Len Network_Packet_Object_xsd.tmp#OptionDataType_Pad1 Network_Packet_Object_xsd.tmp#OptionDataType_PadN Network_Packet_Object_xsd.tmp#OptionDataType
Type PacketObj:OptionDataType
Children PacketObj:Option_Data_Len, PacketObj:Option_Type, PacketObj:Pad1, PacketObj:PadN
Source
 
<xs:element name="Option_Data" type="PacketObj:OptionDataType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Variable-length field, of length such that the complete Hop-by-Hop Options header is an integer multiple of 8 octets long. Contains one or more type-length-value (TLV)-encoded options.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:OptionDataType / PacketObj:Option_Type
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Identifies the type of option. This 8-bit Option Type identifier is internally encoded such that different bits have different meanings. These meanings are further specified in the IPv6OptionType type.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv6OptionType_Do_Not_Recogn_Action Network_Packet_Object_xsd.tmp#IPv6OptionType_Packet_Change Network_Packet_Object_xsd.tmp#IPv6OptionType_Option_Byte Network_Packet_Object_xsd.tmp#IPv6OptionType
Type PacketObj:IPv6OptionType
Children PacketObj:Do_Not_Recogn_Action, PacketObj:Option_Byte, PacketObj:Packet_Change
Source
 
<xs:element name="Option_Type" type="PacketObj:IPv6OptionType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Identifies the type of option. This 8-bit Option Type identifier is internally encoded such that different bits have different meanings. These meanings are further specified in the IPv6OptionType type.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6OptionType / PacketObj:Do_Not_Recogn_Action
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Action to be taken if the processing IPv6 nodes does not recognize the Option Type. This information is internally encoded in the Option Type identifier (highest-order two bits) such that their highest-order two bits specify the action that must be taken if the processing IPv6 node does not recognize the Option type. These possible actions are enumerated via IPv6DoNotRecogActionType.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv6DoNotRecogActionType_datatype Network_Packet_Object_xsd.tmp#IPv6DoNotRecogActionType
Type PacketObj:IPv6DoNotRecogActionType
Type hierarchy
Source
 
<xs:element name="Do_Not_Recogn_Action" type="PacketObj:IPv6DoNotRecogActionType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Action to be taken if the processing IPv6 nodes does not recognize the Option Type. This information is internally encoded in the Option Type identifier (highest-order two bits) such that their highest-order two bits specify the action that must be taken if the processing IPv6 node does not recognize the Option type. These possible actions are enumerated via IPv6DoNotRecogActionType.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6OptionType / PacketObj:Packet_Change
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The third highest order bit of the Option Data specifies whether or not the Option Data of that option can change en-route to the packet's final destination.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv6PacketChangeType_datatype Network_Packet_Object_xsd.tmp#IPv6PacketChangeType
Type PacketObj:IPv6PacketChangeType
Type hierarchy
Source
 
<xs:element name="Packet_Change" type="PacketObj:IPv6PacketChangeType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The third highest order bit of the Option Data specifies whether or not the Option Data of that option can change en-route to the packet's final destination.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6OptionType / PacketObj:Option_Byte
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This field may be used to specify the actual Option Type byte, with no explicit meaning attached. Meaning/interpretation provided by the Do_Not_Recogn_Action and Packet_Change fields.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Option_Byte" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field may be used to specify the actual Option Type byte, with no explicit meaning attached. Meaning/interpretation provided by the Do_Not_Recogn_Action and Packet_Change fields.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:OptionDataType / PacketObj:Option_Data_Len
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Length of the Option Data field of this option, in octets.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Option_Data_Len" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Length of the Option Data field of this option, in octets.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:OptionDataType / PacketObj:Pad1
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Pad1 option is used to insert one octet of padding into the Options area of a header. The Pad1 option does not have length and value fields.
Diagram
Diagram Network_Packet_Object_xsd.tmp#Pad1Type_Octet Network_Packet_Object_xsd.tmp#Pad1Type
Type PacketObj:Pad1Type
Children PacketObj:Octet
Source
 
<xs:element name="Pad1" type="PacketObj:Pad1Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The Pad1 option is used to insert one octet of padding into the Options area of a header. The Pad1 option does not have length and value fields.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:Pad1Type / PacketObj:Octet
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The fixed 00 value specifies that the Pad1 option is used and also serves as the single octet of padding.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Octet" type="cyboxCommon:HexBinaryObjectPropertyType" fixed="00">
  <xs:annotation>
    <xs:documentation>The fixed 00 value specifies that the Pad1 option is used and also serves as the single octet of padding.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:OptionDataType / PacketObj:PadN
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The PadN option is used to insert two or more octets of paddings into the Options area of a header.
Diagram
Diagram Network_Packet_Object_xsd.tmp#PadNType_Octet Network_Packet_Object_xsd.tmp#PadNType_Option_Data_Length Network_Packet_Object_xsd.tmp#PadNType_Option_Data Network_Packet_Object_xsd.tmp#PadNType
Type PacketObj:PadNType
Children PacketObj:Octet, PacketObj:Option_Data, PacketObj:Option_Data_Length
Source
 
<xs:element name="PadN" type="PacketObj:PadNType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The PadN option is used to insert two or more octets of paddings into the Options area of a header.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:PadNType / PacketObj:Octet
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Specifies the PandN option.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Octet" type="cyboxCommon:HexBinaryObjectPropertyType" fixed="01" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Specifies the PandN option.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:PadNType / PacketObj:Option_Data_Length
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Length of the padding. For N octets of padding, the Option_Data_Length fields contains the value N-2.
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Option_Data_Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Length of the padding. For N octets of padding, the Option_Data_Length fields contains the value N-2.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:PadNType / PacketObj:Option_Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Actual padding; consists of N-2 zero-valued octets.
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Option_Data" type="cyboxCommon:IntegerObjectPropertyType" fixed="00" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Actual padding; consists of N-2 zero-valued octets.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6ExtHeaderType / PacketObj:Routing
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Routing header is used by an IPv6 source to list one or more intermediate nodes to be "visited" on the way to a packet's destination. http://tools.ietf.org/html/rfc2460.
Diagram
Diagram Network_Packet_Object_xsd.tmp#RoutingType_Next_Header Network_Packet_Object_xsd.tmp#RoutingType_Header_Ext_Len Network_Packet_Object_xsd.tmp#RoutingType_Routing_Type Network_Packet_Object_xsd.tmp#RoutingType_Segments_Left Network_Packet_Object_xsd.tmp#RoutingType_Type_Specific_Data Network_Packet_Object_xsd.tmp#RoutingType
Type PacketObj:RoutingType
Children PacketObj:Header_Ext_Len, PacketObj:Next_Header, PacketObj:Routing_Type, PacketObj:Segments_Left, PacketObj:Type_Specific_Data
Source
 
<xs:element name="Routing" type="PacketObj:RoutingType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The Routing header is used by an IPv6 source to list one or more intermediate nodes to be "visited" on the way to a packet's destination. http://tools.ietf.org/html/rfc2460.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RoutingType / PacketObj:Next_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Identifies the type of header immediately following the Routing header. Uses the same values as the IPv4 Protocol field.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType_datatype Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType
Type PacketObj:IANAAssignedIPNumbersType
Type hierarchy
Source
 
<xs:element name="Next_Header" type="PacketObj:IANAAssignedIPNumbersType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Identifies the type of header immediately following the Routing header. Uses the same values as the IPv4 Protocol field.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RoutingType / PacketObj:Header_Ext_Len
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
length of the Routing header in 8-octet units, not including the first 8 octets.
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Header_Ext_Len" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>length of the Routing header in 8-octet units, not including the first 8 octets.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RoutingType / PacketObj:Routing_Type
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
8-bit identifiers of a particular Routing header variant. Further definition will be added as required.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Routing_Type" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>8-bit identifiers of a particular Routing header variant. Further definition will be added as required.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RoutingType / PacketObj:Segments_Left
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Number of route segments remaining, i.e., number of explicitly listed intermediate nodes still to be visited before reaching the final destination. http://tools.ietf.org/html/rfc2460.
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Segments_Left" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Number of route segments remaining, i.e., number of explicitly listed intermediate nodes still to be visited before reaching the final destination. http://tools.ietf.org/html/rfc2460.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:RoutingType / PacketObj:Type_Specific_Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Variable length field, of format determined by the Routing Type.
Diagram
Diagram
Type StringObjectPropertyType
Source
 
<xs:element name="Type_Specific_Data" type="cyboxCommon:StringObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Variable length field, of format determined by the Routing Type.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6ExtHeaderType / PacketObj:Fragment
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Fragment header is used by an IPv6 source to send a packet larger than would fit in the path MTU. A fragment packet begins with an unfragmentable part consisting of the IPv6 header plus all extension headers up to and including the routing header. We don't include it for this field because the data is already stored in other elements. We provide the elements necessary for the Fragmentable Part. http://tools.ietf.org/html/rfc2460.
Diagram
Diagram Network_Packet_Object_xsd.tmp#FragmentType_Fragment_Header Network_Packet_Object_xsd.tmp#FragmentType_Fragment Network_Packet_Object_xsd.tmp#FragmentType
Type PacketObj:FragmentType
Children PacketObj:Fragment, PacketObj:Fragment_Header
Source
 
<xs:element name="Fragment" type="PacketObj:FragmentType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The Fragment header is used by an IPv6 source to send a packet larger than would fit in the path MTU. A fragment packet begins with an unfragmentable part consisting of the IPv6 header plus all extension headers up to and including the routing header. We don't include it for this field because the data is already stored in other elements. We provide the elements necessary for the Fragmentable Part. http://tools.ietf.org/html/rfc2460.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:FragmentType / PacketObj:Fragment_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Each fragment has a header containing next header information, the offset of the fragment, an M flag specifying whether or not it is the last fragment, and an identification value.
Diagram
Diagram Network_Packet_Object_xsd.tmp#FragmentHeaderType_Next_Header Network_Packet_Object_xsd.tmp#FragmentHeaderType_Fragment_Offset Network_Packet_Object_xsd.tmp#FragmentHeaderType_M_Flag Network_Packet_Object_xsd.tmp#FragmentHeaderType_Identification Network_Packet_Object_xsd.tmp#FragmentHeaderType
Type PacketObj:FragmentHeaderType
Children PacketObj:Fragment_Offset, PacketObj:Identification, PacketObj:M_Flag, PacketObj:Next_Header
Source
 
<xs:element name="Fragment_Header" type="PacketObj:FragmentHeaderType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Each fragment has a header containing next header information, the offset of the fragment, an M flag specifying whether or not it is the last fragment, and an identification value.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:FragmentHeaderType / PacketObj:Next_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Identifies the type of header immediately following the Fragment header. Uses the same values as the IPv4 Protocol field.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Next_Header" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Identifies the type of header immediately following the Fragment header. Uses the same values as the IPv4 Protocol field.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:FragmentHeaderType / PacketObj:Fragment_Offset
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
13-bit unsigned integer. The offset, in 8-octet units, of the data following this header, relative to the start of the Fragmentable Part or the original packet.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Fragment_Offset" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>13-bit unsigned integer. The offset, in 8-octet units, of the data following this header, relative to the start of the Fragmentable Part or the original packet.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:FragmentHeaderType / PacketObj:M_Flag
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Indicates whether this is the last fragment or whether there are more fragments.
Diagram
Diagram Network_Packet_Object_xsd.tmp#MFlagType_datatype Network_Packet_Object_xsd.tmp#MFlagType
Type PacketObj:MFlagType
Type hierarchy
Source
 
<xs:element name="M_Flag" type="PacketObj:MFlagType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Indicates whether this is the last fragment or whether there are more fragments.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:FragmentHeaderType / PacketObj:Identification
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
For every packet that is to be fragmented, the source node generates a 32-bit Identification value.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Identification" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>For every packet that is to be fragmented, the source node generates a 32-bit Identification value.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:FragmentType / PacketObj:Fragment
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The fragment of the packet that corresponds to the fragment header. The length of the fragment must fit with the MTU of the path to the packets' destination.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Fragment" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The fragment of the packet that corresponds to the fragment header. The length of the fragment must fit with the MTU of the path to the packets' destination.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6ExtHeaderType / PacketObj:Destination_Options
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Destination Options header is used to carry optional information that needs to be examined only by a packet's destination node(s).
Diagram
Diagram Network_Packet_Object_xsd.tmp#DestinationOptionsType_Next_Header Network_Packet_Object_xsd.tmp#DestinationOptionsType_Header_Ext_Len Network_Packet_Object_xsd.tmp#DestinationOptionsType_Option_Data Network_Packet_Object_xsd.tmp#DestinationOptionsType
Type PacketObj:DestinationOptionsType
Children PacketObj:Header_Ext_Len, PacketObj:Next_Header, PacketObj:Option_Data
Source
 
<xs:element name="Destination_Options" type="PacketObj:DestinationOptionsType" minOccurs="0" maxOccurs="2">
  <xs:annotation>
    <xs:documentation>The Destination Options header is used to carry optional information that needs to be examined only by a packet's destination node(s).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:DestinationOptionsType / PacketObj:Next_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Identifies the type of header immediately following the Destination_Options options header. Uses the same values as the IPv4 Protocol field.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType_datatype Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType
Type PacketObj:IANAAssignedIPNumbersType
Type hierarchy
Source
 
<xs:element name="Next_Header" type="PacketObj:IANAAssignedIPNumbersType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Identifies the type of header immediately following the Destination_Options options header. Uses the same values as the IPv4 Protocol field.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:DestinationOptionsType / PacketObj:Header_Ext_Len
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Length of the Destination Options header in 8-octet units, not including the first 8 octets.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Header_Ext_Len" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Length of the Destination Options header in 8-octet units, not including the first 8 octets.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:DestinationOptionsType / PacketObj:Option_Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Variable-length field, of length such that the complete Destinations Options header is an integer multiple of 8 octets long. Contains one or more type-length-value (TLV)-encoded options.
Diagram
Diagram Network_Packet_Object_xsd.tmp#OptionDataType_Option_Type Network_Packet_Object_xsd.tmp#OptionDataType_Option_Data_Len Network_Packet_Object_xsd.tmp#OptionDataType_Pad1 Network_Packet_Object_xsd.tmp#OptionDataType_PadN Network_Packet_Object_xsd.tmp#OptionDataType
Type PacketObj:OptionDataType
Children PacketObj:Option_Data_Len, PacketObj:Option_Type, PacketObj:Pad1, PacketObj:PadN
Source
 
<xs:element name="Option_Data" type="PacketObj:OptionDataType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Variable-length field, of length such that the complete Destinations Options header is an integer multiple of 8 octets long. Contains one or more type-length-value (TLV)-encoded options.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6ExtHeaderType / PacketObj:Authentication_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Follows RFC2402. The IP Authentication Header is used to provide connectionless integrity and data origin authentication for IP datagrams and to provide protection against replays. http://www.ietf.org/rfc/rfc2402.txt.
Diagram
Diagram Network_Packet_Object_xsd.tmp#AuthenticationHeaderType_Next_Header Network_Packet_Object_xsd.tmp#AuthenticationHeaderType_Header_Ext_Len Network_Packet_Object_xsd.tmp#AuthenticationHeaderType_Security_Parameters_Index Network_Packet_Object_xsd.tmp#AuthenticationHeaderType_Sequence_Number Network_Packet_Object_xsd.tmp#AuthenticationHeaderType_Authentication_Data Network_Packet_Object_xsd.tmp#AuthenticationHeaderType
Type PacketObj:AuthenticationHeaderType
Children PacketObj:Authentication_Data, PacketObj:Header_Ext_Len, PacketObj:Next_Header, PacketObj:Security_Parameters_Index, PacketObj:Sequence_Number
Source
 
<xs:element name="Authentication_Header" type="PacketObj:AuthenticationHeaderType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Follows RFC2402. The IP Authentication Header is used to provide connectionless integrity and data origin authentication for IP datagrams and to provide protection against replays. http://www.ietf.org/rfc/rfc2402.txt.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:AuthenticationHeaderType / PacketObj:Next_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Identifies the type of header immediately following the Authentication header. Uses the same values as the IPv4 Protocol field.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType_datatype Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType
Type PacketObj:IANAAssignedIPNumbersType
Type hierarchy
Source
 
<xs:element name="Next_Header" type="PacketObj:IANAAssignedIPNumbersType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Identifies the type of header immediately following the Authentication header. Uses the same values as the IPv4 Protocol field.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:AuthenticationHeaderType / PacketObj:Header_Ext_Len
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
An 8-bit field specifying the length of the AH in 32-bit words.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Header_Ext_Len" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>An 8-bit field specifying the length of the AH in 32-bit words.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:AuthenticationHeaderType / PacketObj:Security_Parameters_Index
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The SPI is an arbitrary 32-bit value that, in combination with the destination IP address and security protocol (AH), uniquely identifies the Security Association for this datagram. The set of SPI values in the range 1 through 255 are reserved by the Internet Assigned Numbers Authority (IANA) for future use. http://www.ietf.org/rfc/rfc2402.txt.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Security_Parameters_Index" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The SPI is an arbitrary 32-bit value that, in combination with the destination IP address and security protocol (AH), uniquely identifies the Security Association for this datagram. The set of SPI values in the range 1 through 255 are reserved by the Internet Assigned Numbers Authority (IANA) for future use. http://www.ietf.org/rfc/rfc2402.txt.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:AuthenticationHeaderType / PacketObj:Sequence_Number
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This unsigned 32-bit field contains a monotonically increasing counter value (sequence number).
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Sequence_Number" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This unsigned 32-bit field contains a monotonically increasing counter value (sequence number).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:AuthenticationHeaderType / PacketObj:Authentication_Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This is a variable-length field that contains the Integrity Check Value (ICV) for this packet. The field must be an integer multiple of 32 bits in length.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Authentication_Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This is a variable-length field that contains the Integrity Check Value (ICV) for this packet. The field must be an integer multiple of 32 bits in length.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6ExtHeaderType / PacketObj:Encapsulating_Security_Payload
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Follows RFC2406. ESP is used to provide confidentiality, data origin authentication, connectionless integrity, an anti-replay service (a form of partial sequence integrity), and limited traffic flow confidentiality.
Diagram
Diagram Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType_Security_Parameters_Index Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType_Sequence_Number Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType_Payload_Data Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType_Padding Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType_Padding_Len Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType_Next_Header Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType_Authentication_Data Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType
Type PacketObj:EncapsulatingSecurityPayloadType
Children PacketObj:Authentication_Data, PacketObj:Next_Header, PacketObj:Padding, PacketObj:Padding_Len, PacketObj:Payload_Data, PacketObj:Security_Parameters_Index, PacketObj:Sequence_Number
Source
 
<xs:element name="Encapsulating_Security_Payload" type="PacketObj:EncapsulatingSecurityPayloadType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Follows RFC2406. ESP is used to provide confidentiality, data origin authentication, connectionless integrity, an anti-replay service (a form of partial sequence integrity), and limited traffic flow confidentiality.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:EncapsulatingSecurityPayloadType / PacketObj:Security_Parameters_Index
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The SPI is an arbitrary 32-bit value that, in combination with the destination IP address and security protocol (ESP), uniquely identifies the Security Association for this datagram. http://www.ietf.org/rfc/rfc2406.txt.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Security_Parameters_Index" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The SPI is an arbitrary 32-bit value that, in combination with the destination IP address and security protocol (ESP), uniquely identifies the Security Association for this datagram. http://www.ietf.org/rfc/rfc2406.txt.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:EncapsulatingSecurityPayloadType / PacketObj:Sequence_Number
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This unsigned 32-bit field contains a monotonically increasing counter value (sequence number).
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Sequence_Number" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This unsigned 32-bit field contains a monotonically increasing counter value (sequence number).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:EncapsulatingSecurityPayloadType / PacketObj:Payload_Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Payload Data is a variable-length field containing data described by the Next Header field.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Payload_Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Payload Data is a variable-length field containing data described by the Next Header field.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:EncapsulatingSecurityPayloadType / PacketObj:Padding
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The padding field can be used for various reasons, such as to fill in the plaintext as required by an encryption algorithm or to conceal the actual length of the payload.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Padding" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The padding field can be used for various reasons, such as to fill in the plaintext as required by an encryption algorithm or to conceal the actual length of the payload.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:EncapsulatingSecurityPayloadType / PacketObj:Padding_Len
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The pad length indicates the number of pad bytes immediately preceding it. Range is 0-255, where a value of zero indicates that no padding bytes are present. http://www.ietf.org/rfc/rfc2406.txt.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Padding_Len" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The pad length indicates the number of pad bytes immediately preceding it. Range is 0-255, where a value of zero indicates that no padding bytes are present. http://www.ietf.org/rfc/rfc2406.txt.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:EncapsulatingSecurityPayloadType / PacketObj:Next_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Identifies the type data contained in the payload data field. Uses the same values as the IPv4 Protocol field.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType_datatype Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType
Type PacketObj:IANAAssignedIPNumbersType
Type hierarchy
Source
 
<xs:element name="Next_Header" type="PacketObj:IANAAssignedIPNumbersType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Identifies the type data contained in the payload data field. Uses the same values as the IPv4 Protocol field.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:EncapsulatingSecurityPayloadType / PacketObj:Authentication_Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Authentication Data is a variable-length field containing an Integrity Check Value (ICV) computed over the ESP packet minus the Authentication Data. http://www.ietf.org/rfc/rfc2406.txt.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Authentication_Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The Authentication Data is a variable-length field containing an Integrity Check Value (ICV) computed over the ESP packet minus the Authentication Data. http://www.ietf.org/rfc/rfc2406.txt.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:IPv6PacketType / PacketObj:Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The data portion of an IP packet. Actual field values will probably be specified in the elements of the different network layers, but we provide a field here to capture any data as necessary.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The data portion of an IP packet. Actual field values will probably be specified in the elements of the different network layers, but we provide a field here to capture any data as necessary.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:InternetLayerType / PacketObj:ICMPv6
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ICMPv6 is the implementation of the ICMP for IPv6. ICMPv6 performs error reporting and diagnostic functions.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6PacketType_ICMPv6_Header Network_Packet_Object_xsd.tmp#ICMPv6PacketType_Error_Msg Network_Packet_Object_xsd.tmp#ICMPv6PacketType_Info_Msg Network_Packet_Object_xsd.tmp#ICMPv6PacketType
Type PacketObj:ICMPv6PacketType
Children PacketObj:Error_Msg, PacketObj:ICMPv6_Header, PacketObj:Info_Msg
Source
 
<xs:element name="ICMPv6" type="PacketObj:ICMPv6PacketType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>ICMPv6 is the implementation of the ICMP for IPv6. ICMPv6 performs error reporting and diagnostic functions.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6PacketType / PacketObj:ICMPv6_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Actual ICMP v6 header bytes are defined, corresponding to the ICMP type, ICMP code, and to the checksum.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6HeaderType_Type Network_Packet_Object_xsd.tmp#ICMPv6HeaderType_Code Network_Packet_Object_xsd.tmp#ICMPv6HeaderType_Checksum Network_Packet_Object_xsd.tmp#ICMPv6HeaderType
Type PacketObj:ICMPv6HeaderType
Children PacketObj:Checksum, PacketObj:Code, PacketObj:Type
Source
 
<xs:element name="ICMPv6_Header" type="PacketObj:ICMPv6HeaderType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Actual ICMP v6 header bytes are defined, corresponding to the ICMP type, ICMP code, and to the checksum.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6PacketType / PacketObj:Error_Msg
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
For ICMP v6 error messages, boolean values are used in this field to explicitly interpret the type and code bytes appearing in the ICMP header. Additional fields and message content are also defined here. The type value indicates whether an ICMP message is an error message (type is 0 to 127) or an information message (type is 128 to 255).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6ErrorMessageType_Destination_Unreachable Network_Packet_Object_xsd.tmp#ICMPv6ErrorMessageType_Packet_Too_Big Network_Packet_Object_xsd.tmp#ICMPv6ErrorMessageType_Time_Exceeded Network_Packet_Object_xsd.tmp#ICMPv6ErrorMessageType_Parameter_Problem Network_Packet_Object_xsd.tmp#ICMPv6ErrorMessageType_Invoking_Packet Network_Packet_Object_xsd.tmp#ICMPv6ErrorMessageType
Type PacketObj:ICMPv6ErrorMessageType
Children PacketObj:Destination_Unreachable, PacketObj:Invoking_Packet, PacketObj:Packet_Too_Big, PacketObj:Parameter_Problem, PacketObj:Time_Exceeded
Source
 
<xs:element name="Error_Msg" type="PacketObj:ICMPv6ErrorMessageType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>For ICMP v6 error messages, boolean values are used in this field to explicitly interpret the type and code bytes appearing in the ICMP header. Additional fields and message content are also defined here. The type value indicates whether an ICMP message is an error message (type is 0 to 127) or an information message (type is 128 to 255).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6ErrorMessageType / PacketObj:Destination_Unreachable
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
A destination unreachable message should be generated by a router, or by the IPv6 later in the originating node, in response to a packet that cannot be delivered to its destination address for reasons other than congestion. (http://tools.ietf.org/html/rfc4443).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType_No_Route Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType_Comm_Prohibited Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType_Beyond_Scope Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType_Address_Unreachable Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType_Port_Unreachable Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType_Src_Addr_Failed_Policy Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType_Reject_Route Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType
Type PacketObj:ICMPv6DestinationUnreachableType
Children PacketObj:Address_Unreachable, PacketObj:Beyond_Scope, PacketObj:Comm_Prohibited, PacketObj:No_Route, PacketObj:Port_Unreachable, PacketObj:Reject_Route, PacketObj:Src_Addr_Failed_Policy
Source
 
<xs:element name="Destination_Unreachable" type="PacketObj:ICMPv6DestinationUnreachableType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>A destination unreachable message should be generated by a router, or by the IPv6 later in the originating node, in response to a packet that cannot be delivered to its destination address for reasons other than congestion. (http://tools.ietf.org/html/rfc4443).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6DestinationUnreachableType / PacketObj:No_Route
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
No route to destination (ICMP v6 code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="No_Route" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>No route to destination (ICMP v6 code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6DestinationUnreachableType / PacketObj:Comm_Prohibited
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Communication with destination administratively prohibited (ICMP v6 code=1).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Comm_Prohibited" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Communication with destination administratively prohibited (ICMP v6 code=1).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6DestinationUnreachableType / PacketObj:Beyond_Scope
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Beyond scope of source address (ICMP v6 code =2).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Beyond_Scope" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Beyond scope of source address (ICMP v6 code =2).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6DestinationUnreachableType / PacketObj:Address_Unreachable
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Address is unreachable (ICMP v6 code=3).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Address_Unreachable" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Address is unreachable (ICMP v6 code=3).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6DestinationUnreachableType / PacketObj:Port_Unreachable
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Port is unreachable (ICMP v6 code=4).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Port_Unreachable" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Port is unreachable (ICMP v6 code=4).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6DestinationUnreachableType / PacketObj:Src_Addr_Failed_Policy
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Source address failed ingress/egress policy (ICMP v6 code=5).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Src_Addr_Failed_Policy" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Source address failed ingress/egress policy (ICMP v6 code=5).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6DestinationUnreachableType / PacketObj:Reject_Route
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Reject route to destination (ICMP v6 code=6).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Reject_Route" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Reject route to destination (ICMP v6 code=6).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6ErrorMessageType / PacketObj:Packet_Too_Big
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
A packet too big message must be sent by a router in response to a packet that it cannot forward because the packet is larger than the MTU of the outgoing link.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6PacketTooBigType_Packet_Too_Big Network_Packet_Object_xsd.tmp#ICMPv6PacketTooBigType_MTU Network_Packet_Object_xsd.tmp#ICMPv6PacketTooBigType
Type PacketObj:ICMPv6PacketTooBigType
Children PacketObj:MTU, PacketObj:Packet_Too_Big
Source
 
<xs:element name="Packet_Too_Big" type="PacketObj:ICMPv6PacketTooBigType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>A packet too big message must be sent by a router in response to a packet that it cannot forward because the packet is larger than the MTU of the outgoing link.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6PacketTooBigType / PacketObj:Packet_Too_Big
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Only one code value is defined and is set to 0 (zero) by the originator and ignored by the receiver.
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Packet_Too_Big" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Only one code value is defined and is set to 0 (zero) by the originator and ignored by the receiver.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6PacketTooBigType / PacketObj:MTU
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Maximum Transmission Unit describes the size limit for any given physical network.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="MTU" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Maximum Transmission Unit describes the size limit for any given physical network.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6ErrorMessageType / PacketObj:Time_Exceeded
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
A time exceeded message is send if either the hop limit is exceeded (hop limit = 0) or if fragment reassembly has timed out.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6TimeExceededType_Hop_Limit_Exceeded Network_Packet_Object_xsd.tmp#ICMPv6TimeExceededType_Fragment_Reassem_Time_Exceeded Network_Packet_Object_xsd.tmp#ICMPv6TimeExceededType
Type PacketObj:ICMPv6TimeExceededType
Children PacketObj:Fragment_Reassem_Time_Exceeded, PacketObj:Hop_Limit_Exceeded
Source
 
<xs:element name="Time_Exceeded" type="PacketObj:ICMPv6TimeExceededType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>A time exceeded message is send if either the hop limit is exceeded (hop limit = 0) or if fragment reassembly has timed out.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6TimeExceededType / PacketObj:Hop_Limit_Exceeded
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Hop limit exceeded in transit (ICMP v6 code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Hop_Limit_Exceeded" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Hop limit exceeded in transit (ICMP v6 code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6TimeExceededType / PacketObj:Fragment_Reassem_Time_Exceeded
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Fragment reassembly time exceeded (ICMP v6 code=1).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Fragment_Reassem_Time_Exceeded" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Fragment reassembly time exceeded (ICMP v6 code=1).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6ErrorMessageType / PacketObj:Parameter_Problem
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
If an IPv6 node processing a packet finds a problem with a field in the IPv6 header or extension headers and it cannot complete processing of the packet, it should send an ICMPv6 Parameter Problem message to the packet's source (http://tools.ietf.org/html/rfc4443).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6ParameterProblemType_Erroneous_Header_Field Network_Packet_Object_xsd.tmp#ICMPv6ParameterProblemType_Unrecognized_Next_Header_Type Network_Packet_Object_xsd.tmp#ICMPv6ParameterProblemType_Unrecognized_IPv6_Option Network_Packet_Object_xsd.tmp#ICMPv6ParameterProblemType_Pointer Network_Packet_Object_xsd.tmp#ICMPv6ParameterProblemType
Type PacketObj:ICMPv6ParameterProblemType
Children PacketObj:Erroneous_Header_Field, PacketObj:Pointer, PacketObj:Unrecognized_IPv6_Option, PacketObj:Unrecognized_Next_Header_Type
Source
 
<xs:element name="Parameter_Problem" type="PacketObj:ICMPv6ParameterProblemType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>If an IPv6 node processing a packet finds a problem with a field in the IPv6 header or extension headers and it cannot complete processing of the packet, it should send an ICMPv6 Parameter Problem message to the packet's source (http://tools.ietf.org/html/rfc4443).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6ParameterProblemType / PacketObj:Erroneous_Header_Field
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Erroneous header field encountered (ICMP v6 code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Erroneous_Header_Field" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Erroneous header field encountered (ICMP v6 code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6ParameterProblemType / PacketObj:Unrecognized_Next_Header_Type
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Unrecognized next header type encountered (ICMP v6 code=1).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Unrecognized_Next_Header_Type" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Unrecognized next header type encountered (ICMP v6 code=1).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6ParameterProblemType / PacketObj:Unrecognized_IPv6_Option
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Unrecognized IP v6 option encountered (ICMP v6 code=2).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Unrecognized_IPv6_Option" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Unrecognized IP v6 option encountered (ICMP v6 code=2).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6ParameterProblemType / PacketObj:Pointer
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
identifies octet offset within invoking packet where error was detected.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Pointer" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>identifies octet offset within invoking packet where error was detected.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6ErrorMessageType / PacketObj:Invoking_Packet
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPc6 MTU.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Invoking_Packet" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPc6 MTU.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6PacketType / PacketObj:Info_Msg
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
For ICMP v6 informational messages, boolean values are used in this field to explicitly interpret the type and code bytes appearing in the ICMP header. Additional fields and message content are also defined here. The type value indicates whether an ICMP message is an error message (type is 0 to 127) or an information message (type is 128 to 255).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6InfoMessageType_Echo_Request Network_Packet_Object_xsd.tmp#ICMPv6InfoMessageType_Echo_Reply Network_Packet_Object_xsd.tmp#ICMPv6InfoMessageType_Info_Msg_Content Network_Packet_Object_xsd.tmp#ICMPv6InfoMessageType
Type PacketObj:ICMPv6InfoMessageType
Children PacketObj:Echo_Reply, PacketObj:Echo_Request, PacketObj:Info_Msg_Content
Source
 
<xs:element name="Info_Msg" type="PacketObj:ICMPv6InfoMessageType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>For ICMP v6 informational messages, boolean values are used in this field to explicitly interpret the type and code bytes appearing in the ICMP header. Additional fields and message content are also defined here. The type value indicates whether an ICMP message is an error message (type is 0 to 127) or an information message (type is 128 to 255).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6InfoMessageType / PacketObj:Echo_Request
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Echo request and reply messages are used for diagnostic purposes.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6EchoRequestType_Echo_Request Network_Packet_Object_xsd.tmp#ICMPv6EchoRequestType_Data Network_Packet_Object_xsd.tmp#ICMPv6EchoRequestType
Type PacketObj:ICMPv6EchoRequestType
Children PacketObj:Data, PacketObj:Echo_Request
Source
 
<xs:element name="Echo_Request" type="PacketObj:ICMPv6EchoRequestType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Echo request and reply messages are used for diagnostic purposes.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6EchoRequestType / PacketObj:Echo_Request
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Every node must implement an ICMP v6 Echo responder function that receives Echo Requests (ICMP v6 code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Echo_Request" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Every node must implement an ICMP v6 Echo responder function that receives Echo Requests (ICMP v6 code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6EchoRequestType / PacketObj:Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Zero or more octets of arbitrary data.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Zero or more octets of arbitrary data.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6InfoMessageType / PacketObj:Echo_Reply
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Echo request and reply messages are used for diagnostic purposes.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6EchoReplyType_Echo_Reply Network_Packet_Object_xsd.tmp#ICMPv6EchoReplyType_Data Network_Packet_Object_xsd.tmp#ICMPv6EchoReplyType
Type PacketObj:ICMPv6EchoReplyType
Children PacketObj:Data, PacketObj:Echo_Reply
Source
 
<xs:element name="Echo_Reply" type="PacketObj:ICMPv6EchoReplyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Echo request and reply messages are used for diagnostic purposes.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6EchoReplyType / PacketObj:Echo_Reply
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Every node must implement an ICMP v6 Echo responder function that originates corresponding Echo Replies(ICMP v6 code=0).
Diagram
Diagram
Type xs:boolean
Source
 
<xs:element name="Echo_Reply" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Every node must implement an ICMP v6 Echo responder function that originates corresponding Echo Replies(ICMP v6 code=0).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6EchoReplyType / PacketObj:Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This is the data from the invoking echo request message.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This is the data from the invoking echo request message.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6InfoMessageType / PacketObj:Info_Msg_Content
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Fields that are common to all ICMP v6 informational messages are defined here. Fields that are specific to individual messages are defined separately under each message type.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6InfoMessageContentType_Identifier Network_Packet_Object_xsd.tmp#ICMPv6InfoMessageContentType_Sequence_Number Network_Packet_Object_xsd.tmp#ICMPv6InfoMessageContentType
Type PacketObj:ICMPv6InfoMessageContentType
Children PacketObj:Identifier, PacketObj:Sequence_Number
Source
 
<xs:element name="Info_Msg_Content" type="PacketObj:ICMPv6InfoMessageContentType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Fields that are common to all ICMP v6 informational messages are defined here. Fields that are specific to individual messages are defined separately under each message type.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6InfoMessageContentType / PacketObj:Identifier
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
16-bit identifier. Combined with the sequence number, called the "quench" for echo reply and echo request.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Identifier" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>16-bit identifier. Combined with the sequence number, called the "quench" for echo reply and echo request.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:ICMPv6InfoMessageContentType / PacketObj:Sequence_Number
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
16-bit sequence number. The identifier and sequence number can be used by the client to match the reply with the request that caused the reply.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Sequence_Number" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>16-bit sequence number. The identifier and sequence number can be used by the client to match the reply with the request that caused the reply.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:NetworkPacketObjectType / PacketObj:Transport_Layer
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Transport layer characterizes information about the transport layer of this Network Packet. The transport layer is one layer from the 7-layer OSI Model.
Diagram
Diagram Network_Packet_Object_xsd.tmp#TransportLayerType_TCP Network_Packet_Object_xsd.tmp#TransportLayerType_UDP Network_Packet_Object_xsd.tmp#TransportLayerType
Type PacketObj:TransportLayerType
Children PacketObj:TCP, PacketObj:UDP
Source
 
<xs:element name="Transport_Layer" type="PacketObj:TransportLayerType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Transport layer characterizes information about the transport layer of this Network Packet. The transport layer is one layer from the 7-layer OSI Model.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TransportLayerType / PacketObj:TCP
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
TCP provides reliable, ordered delivery of a stream of bytes from a program on one computer to another program on another computer. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
Diagram
Diagram Network_Packet_Object_xsd.tmp#TCPType_TCP_Header Network_Packet_Object_xsd.tmp#TCPType_Options Network_Packet_Object_xsd.tmp#TCPType_Data Network_Packet_Object_xsd.tmp#TCPType
Type PacketObj:TCPType
Children PacketObj:Data, PacketObj:Options, PacketObj:TCP_Header
Source
 
<xs:element name="TCP" type="PacketObj:TCPType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>TCP provides reliable, ordered delivery of a stream of bytes from a program on one computer to another program on another computer. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TCPType / PacketObj:TCP_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The TCP header contains 10 mandatory fields and an optional extension field. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
Diagram
Diagram Network_Packet_Object_xsd.tmp#TCPHeaderType_Src_Port Network_Packet_Object_xsd.tmp#TCPHeaderType_Dest_Port Network_Packet_Object_xsd.tmp#TCPHeaderType_Seq_Num Network_Packet_Object_xsd.tmp#TCPHeaderType_ACK_Num Network_Packet_Object_xsd.tmp#TCPHeaderType_Data_Offset Network_Packet_Object_xsd.tmp#TCPHeaderType_Reserved Network_Packet_Object_xsd.tmp#TCPHeaderType_TCP_Flags Network_Packet_Object_xsd.tmp#TCPHeaderType_Window Network_Packet_Object_xsd.tmp#TCPHeaderType_Checksum Network_Packet_Object_xsd.tmp#TCPHeaderType_Urg_Ptr Network_Packet_Object_xsd.tmp#TCPHeaderType
Type PacketObj:TCPHeaderType
Children PacketObj:ACK_Num, PacketObj:Checksum, PacketObj:Data_Offset, PacketObj:Dest_Port, PacketObj:Reserved, PacketObj:Seq_Num, PacketObj:Src_Port, PacketObj:TCP_Flags, PacketObj:Urg_Ptr, PacketObj:Window
Source
 
<xs:element name="TCP_Header" type="PacketObj:TCPHeaderType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The TCP header contains 10 mandatory fields and an optional extension field. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TCPHeaderType / PacketObj:Src_Port
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Identifies the sending port.
Diagram
Diagram
Type PortObjectType
Source
 
<xs:element name="Src_Port" type="PortObj:PortObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Identifies the sending port.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TCPHeaderType / PacketObj:Dest_Port
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Identifies the receiving port.
Diagram
Diagram
Type PortObjectType
Source
 
<xs:element name="Dest_Port" type="PortObj:PortObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Identifies the receiving port.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TCPHeaderType / PacketObj:Seq_Num
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Sequence number (32-bits) has a dual role: If the SYN flag is set, then this is the initial sequence numbers. If the SYN flag is clear (see Control Bits element), then this is the accumulated sequence number of the first data byte of this packet for the current session. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Seq_Num" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The Sequence number (32-bits) has a dual role: If the SYN flag is set, then this is the initial sequence numbers. If the SYN flag is clear (see Control Bits element), then this is the accumulated sequence number of the first data byte of this packet for the current session. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TCPHeaderType / PacketObj:ACK_Num
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
If the ACK flag (see Control Bits element) is set then the value of this field is the next sequence number that the receiver is expecting.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="ACK_Num" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>If the ACK flag (see Control Bits element) is set then the value of this field is the next sequence number that the receiver is expecting.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TCPHeaderType / PacketObj:Data_Offset
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Specifies the size of the TCP header in 32-bit words.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Data_Offset" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Specifies the size of the TCP header in 32-bit words.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TCPHeaderType / PacketObj:Reserved
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
these 3 bits are reserved for future use and should be set to zero.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Reserved" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>these 3 bits are reserved for future use and should be set to zero.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TCPHeaderType / PacketObj:TCP_Flags
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The TCP header contains 9 flags (aka Control Bits).
Diagram
Diagram Network_Packet_Object_xsd.tmp#TCPFlagsType_ns Network_Packet_Object_xsd.tmp#TCPFlagsType_cwr Network_Packet_Object_xsd.tmp#TCPFlagsType_ece Network_Packet_Object_xsd.tmp#TCPFlagsType_urg Network_Packet_Object_xsd.tmp#TCPFlagsType_ack Network_Packet_Object_xsd.tmp#TCPFlagsType_psh Network_Packet_Object_xsd.tmp#TCPFlagsType_rst Network_Packet_Object_xsd.tmp#TCPFlagsType_syn Network_Packet_Object_xsd.tmp#TCPFlagsType_fin Network_Packet_Object_xsd.tmp#TCPFlagsType
Type PacketObj:TCPFlagsType
Attributes
QName Type Use Annotation
ack xs:boolean optional 
indicates that the Acknowledgment field is significant. All packets after the initial SYN packet sent by the client should have this flag set. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
cwr xs:boolean optional 
Congestion Window Reduced (CWR) flag is set by the sending host to indicate that it received a TCP segment with the ECE flag set and had responded in congestion control mechanism. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
ece xs:boolean optional 
ECN-Echo indicates: if the SYN flag is set, that the TCP peer is ECN capable; if the SYN flag is clear, that a packet with Congestion Experienced flag in IP header set is received during normal transmission. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
fin xs:boolean optional 
If this flag is set, it means there is no more data from sender.
ns xs:boolean optional 
ECN-nonce concealment protection.
psh xs:boolean optional 
Push functions. asks to push the buffered dtata to the receiving application. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
rst xs:boolean optional 
Reset the connection.
syn xs:boolean optional 
Synchronize sequence numbers. Only the first packet sent from each end should have this flag set. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
urg xs:boolean optional 
Indicates that the Urgent point field is significant.
Source
 
<xs:element name="TCP_Flags" type="PacketObj:TCPFlagsType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The TCP header contains 9 flags (aka Control Bits).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TCPHeaderType / PacketObj:Window
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The size of the receive window, which specifies the number of bytes (beyond the sequence number in the acknowledgment field) that the sender of this segment is currently willing to receive. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Window" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The size of the receive window, which specifies the number of bytes (beyond the sequence number in the acknowledgment field) that the sender of this segment is currently willing to receive. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TCPHeaderType / PacketObj:Checksum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The 16-bit checksum field is used for error-checking of the header and data. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Checksum" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The 16-bit checksum field is used for error-checking of the header and data. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TCPHeaderType / PacketObj:Urg_Ptr
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
If the URG flag is set, then this 16-bit field is an offset from the sequence number indicating the last urgent data byte. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Urg_Ptr" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>If the URG flag is set, then this 16-bit field is an offset from the sequence number indicating the last urgent data byte. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TCPType / PacketObj:Options
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Options have up to three fields: Option-Kind (1 byte), Option-Length (1 byte), Option-Data (variable). This field will be further defined when required.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Options" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Options have up to three fields: Option-Kind (1 byte), Option-Length (1 byte), Option-Data (variable). This field will be further defined when required.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TCPType / PacketObj:Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Data field specifies the data payload of the TCP packet.
Diagram
Diagram
Type DataSegmentType
Source
 
<xs:element name="Data" type="cyboxCommon:DataSegmentType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The Data field specifies the data payload of the TCP packet.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:TransportLayerType / PacketObj:UDP
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
UDP uses a simple transmission model without implicit handshaking dialogues for providing reliability, ordering, or data integrity. Thus, UDP provides an unreliable service and datagrams may arrive out of order, appear duplicated, or go missing without notice. http://en.wikipedia.org/wiki/User_Datagram_Protocol.
Diagram
Diagram Network_Packet_Object_xsd.tmp#UDPType_UDP_Header Network_Packet_Object_xsd.tmp#UDPType_Data Network_Packet_Object_xsd.tmp#UDPType
Type PacketObj:UDPType
Children PacketObj:Data, PacketObj:UDP_Header
Source
 
<xs:element name="UDP" type="PacketObj:UDPType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>UDP uses a simple transmission model without implicit handshaking dialogues for providing reliability, ordering, or data integrity. Thus, UDP provides an unreliable service and datagrams may arrive out of order, appear duplicated, or go missing without notice. http://en.wikipedia.org/wiki/User_Datagram_Protocol.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:UDPType / PacketObj:UDP_Header
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The UDP header consists of four fields, which are defined here.
Diagram
Diagram Network_Packet_Object_xsd.tmp#UDPHeaderType_SrcPort Network_Packet_Object_xsd.tmp#UDPHeaderType_DestPort Network_Packet_Object_xsd.tmp#UDPHeaderType_Length Network_Packet_Object_xsd.tmp#UDPHeaderType_Checksum Network_Packet_Object_xsd.tmp#UDPHeaderType
Type PacketObj:UDPHeaderType
Children PacketObj:Checksum, PacketObj:DestPort, PacketObj:Length, PacketObj:SrcPort
Source
 
<xs:element name="UDP_Header" type="PacketObj:UDPHeaderType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The UDP header consists of four fields, which are defined here.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:UDPHeaderType / PacketObj:SrcPort
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Identifies the sender's port.
Diagram
Diagram
Type PortObjectType
Source
 
<xs:element name="SrcPort" type="PortObj:PortObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Identifies the sender's port.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:UDPHeaderType / PacketObj:DestPort
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Identifies the receiver's port.
Diagram
Diagram
Type PortObjectType
Source
 
<xs:element name="DestPort" type="PortObj:PortObjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Identifies the receiver's port.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:UDPHeaderType / PacketObj:Length
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Specifies the length in bytes of the entire datagram (header and data).
Diagram
Diagram
Type IntegerObjectPropertyType
Source
 
<xs:element name="Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Specifies the length in bytes of the entire datagram (header and data).</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:UDPHeaderType / PacketObj:Checksum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The checksum is used for error-checking of the header and data.
Diagram
Diagram
Type HexBinaryObjectPropertyType
Source
 
<xs:element name="Checksum" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The checksum is used for error-checking of the header and data.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PacketObj:UDPType / PacketObj:Data
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Data field specifies the data payload of the UDP packet.
Diagram
Diagram
Type DataSegmentType
Source
 
<xs:element name="Data" type="cyboxCommon:DataSegmentType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The Data field specifies the data payload of the UDP packet.</xs:documentation>
  </xs:annotation>
</xs:element>
Complex Type PacketObj:NetworkPacketObjectType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The NetworkPacketObjectType's definition of a network packet is based on the TCP/IP model/Internet protocol suite. In the TCP/IP stack, "packet" is generally defined as IP header plus payload, but we also include the LinkLayer from the OSI model, which defines the physical network interfaces and routing protocols. Protocol fields are provided but requirements are not enforced/captured; all fields are optional.
Diagram
Diagram Network_Packet_Object_xsd.tmp#NetworkPacketObjectType_Link_Layer Network_Packet_Object_xsd.tmp#NetworkPacketObjectType_Internet_Layer Network_Packet_Object_xsd.tmp#NetworkPacketObjectType_Transport_Layer
Type extension of ObjectPropertiesType
Type hierarchy
Used by
Children PacketObj:Internet_Layer, PacketObj:Link_Layer, PacketObj:Transport_Layer
Source
 
<xs:complexType name="NetworkPacketObjectType">
  <xs:annotation>
    <xs:documentation>The NetworkPacketObjectType's definition of a network packet is based on the TCP/IP model/Internet protocol suite. In the TCP/IP stack, "packet" is generally defined as IP header plus payload, but we also include the LinkLayer from the OSI model, which defines the physical network interfaces and routing protocols. Protocol fields are provided but requirements are not enforced/captured; all fields are optional.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="cyboxCommon:ObjectPropertiesType">
      <xs:choice>
        <xs:element name="Link_Layer" type="PacketObj:LinkLayerType" minOccurs="0">
          <xs:annotation>
            <xs:documentation>The Link Layer is the lowest layer of the TCP/IP network stack and is comprised of physical and logical protocols that operate between adjacent nodes of a network segment or a WAN connection.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="Internet_Layer" type="PacketObj:InternetLayerType" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Internet layer characterizes information about the network layer of this Network Packet. The network layer is one layer from the 7-layer OSI Model.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="Transport_Layer" type="PacketObj:TransportLayerType" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Transport layer characterizes information about the transport layer of this Network Packet. The transport layer is one layer from the 7-layer OSI Model.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:choice>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type PacketObj:LinkLayerType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
A link layer protocol is a hardware interface protocol, such as Ethernet, or a logical link routing protocol, such as ARP.
Diagram
Diagram Network_Packet_Object_xsd.tmp#LinkLayerType_Physical_Interface Network_Packet_Object_xsd.tmp#LinkLayerType_Logical_Protocols
Used by
Children PacketObj:Logical_Protocols, PacketObj:Physical_Interface
Source
 
<xs:complexType name="LinkLayerType">
  <xs:annotation>
    <xs:documentation>A link layer protocol is a hardware interface protocol, such as Ethernet, or a logical link routing protocol, such as ARP.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="Physical_Interface" type="PacketObj:PhysicalInterfaceType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Physical Interface characterizes one hardware interface of a link layer connection.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Logical_Protocols" type="PacketObj:LogicalProtocolType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Logical Protocols characterizes the logical protocol of a link layer connection. One example of a logical protocol is ARP.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:PhysicalInterfaceType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Multiple interface types exist - only most common (Ethernet) included now. Others will be added later as needed.
Diagram
Diagram Network_Packet_Object_xsd.tmp#PhysicalInterfaceType_Ethernet
Used by
Children PacketObj:Ethernet
Source
 
<xs:complexType name="PhysicalInterfaceType">
  <xs:annotation>
    <xs:documentation>Multiple interface types exist - only most common (Ethernet) included now. Others will be added later as needed.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="Ethernet" type="PacketObj:EthernetInterfaceType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Ethernet sends network packets from the sending host to one or more receiving hosts. (REF: IEEE 802.3; http://wiki.wireshark.org/Ethernet).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:EthernetInterfaceType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Ethernet sends network packets from the sending host to one or more receiving hosts. (REF: IEEE 802.3; http://wiki.wireshark.org/Ethernet).
Diagram
Diagram Network_Packet_Object_xsd.tmp#EthernetInterfaceType_Ethernet_Header
Used by
Children PacketObj:Ethernet_Header
Source
 
<xs:complexType name="EthernetInterfaceType">
  <xs:annotation>
    <xs:documentation>Ethernet sends network packets from the sending host to one or more receiving hosts. (REF: IEEE 802.3; http://wiki.wireshark.org/Ethernet).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Ethernet_Header" type="PacketObj:EthernetHeaderType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The ethernet header includes information such as source MAC address, destination MAC address, and more.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:EthernetHeaderType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Ethernet header characterizes and ethernet header and includes information such as source MAC address, destination MAC address, and more.
Diagram
Diagram Network_Packet_Object_xsd.tmp#EthernetHeaderType_Destination_MAC_Addr Network_Packet_Object_xsd.tmp#EthernetHeaderType_Source_MAC_Addr Network_Packet_Object_xsd.tmp#EthernetHeaderType_Type_Or_Length Network_Packet_Object_xsd.tmp#EthernetHeaderType_Checksum
Used by
Children PacketObj:Checksum, PacketObj:Destination_MAC_Addr, PacketObj:Source_MAC_Addr, PacketObj:Type_Or_Length
Source
 
<xs:complexType name="EthernetHeaderType">
  <xs:annotation>
    <xs:documentation>Ethernet header characterizes and ethernet header and includes information such as source MAC address, destination MAC address, and more.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Destination_MAC_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Destination MAC Addr characterizes the destination MAC Address of the ethernet frame.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Source_MAC_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Source MAC Addr characterizes the source MAC Address of the ethernet frame.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Type_Or_Length" type="PacketObj:TypeLengthType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Type or Length characterizes either the length of the ethernet frame or the protocol type of the network layer.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Checksum" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Checksum characterizes the Frame Check sequence of an ethernet frame.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:TypeLengthType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
0-1500 then it is a length field. Otherwise, it defines the protocol type of the Internet layer.
Diagram
Diagram Network_Packet_Object_xsd.tmp#TypeLengthType_Length Network_Packet_Object_xsd.tmp#TypeLengthType_Internet_Layer_Type
Used by
Children PacketObj:Internet_Layer_Type, PacketObj:Length
Source
 
<xs:complexType name="TypeLengthType">
  <xs:annotation>
    <xs:documentation>0-1500 then it is a length field. Otherwise, it defines the protocol type of the Internet layer.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="Length" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Length characterizes the length of the ethernet frame.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Internet_Layer_Type" type="PacketObj:IANAEtherType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>two-octet field in an Ethernet frame. specifies protocol encapsulated in the payload of ethernet frame.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:IANAEtherType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
EtherObjectType specifies "type" field of Ethernets, via a union of the IANAEtherTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IANAEtherType_datatype
Type restriction of BaseObjectPropertyType
Type hierarchy
Used by
Source
 
<xs:complexType name="IANAEtherType">
  <xs:annotation>
    <xs:documentation>EtherObjectType specifies "type" field of Ethernets, via a union of the IANAEtherTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:restriction base="cyboxCommon:BaseObjectPropertyType">
      <xs:simpleType>
        <xs:union memberTypes="PacketObj:IANAEtherTypeEnum xs:string"/>
      </xs:simpleType>
      <xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
        <xs:annotation>
          <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
  </xs:simpleContent>
</xs:complexType>
Complex Type PacketObj:LogicalProtocolType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Logical Protocols characterizes the logical protocol of a link layer connection. One example of a logical protocol is ARP.
Diagram
Diagram Network_Packet_Object_xsd.tmp#LogicalProtocolType_ARP_RARP Network_Packet_Object_xsd.tmp#LogicalProtocolType_NDP
Used by
Children PacketObj:ARP_RARP, PacketObj:NDP
Source
 
<xs:complexType name="LogicalProtocolType">
  <xs:annotation>
    <xs:documentation>Logical Protocols characterizes the logical protocol of a link layer connection. One example of a logical protocol is ARP.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="ARP_RARP" type="PacketObj:ARPType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>ARP is a logical protocol used for resolution of network layer addresses (e.g., IP addresses) into link layer addresses (e.g., MAC addresses). RARP is a logical protocol used by a host computer to request its network layer address when it has its link layer address.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="NDP" type="PacketObj:NDPType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Neighbor Discovery Protocol (NDP) is used with IPv6 to determine the link-layer addresses for neighbors. Corresponds to combination of IPv4 protocols: ARP, ICMP Router Discovery, and ICMP Redirect.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:ARPType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Address Resolution Protocol is a request and reply protocol that runs encapsulated by the line protocol. It is communicated within the boundaries of a single network, never routed across internetwork nodes. This property places ARP into the Link Layer. It is encapsulated. REF: http://www.comptechdoc.org/independent/networking/guide/netarp.html.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ARPType_Hardware_Addr_Type Network_Packet_Object_xsd.tmp#ARPType_Proto_Addr_Type Network_Packet_Object_xsd.tmp#ARPType_Hardware_Addr_Size Network_Packet_Object_xsd.tmp#ARPType_Proto_Addr_Size Network_Packet_Object_xsd.tmp#ARPType_Op_Type Network_Packet_Object_xsd.tmp#ARPType_Sender_Hardware_Addr Network_Packet_Object_xsd.tmp#ARPType_Sender_Protocol_Addr Network_Packet_Object_xsd.tmp#ARPType_Recip_Hardware_Addr Network_Packet_Object_xsd.tmp#ARPType_Recip_Protocol_Addr
Used by
Children PacketObj:Hardware_Addr_Size, PacketObj:Hardware_Addr_Type, PacketObj:Op_Type, PacketObj:Proto_Addr_Size, PacketObj:Proto_Addr_Type, PacketObj:Recip_Hardware_Addr, PacketObj:Recip_Protocol_Addr, PacketObj:Sender_Hardware_Addr, PacketObj:Sender_Protocol_Addr
Source
 
<xs:complexType name="ARPType">
  <xs:annotation>
    <xs:documentation>The Address Resolution Protocol is a request and reply protocol that runs encapsulated by the line protocol. It is communicated within the boundaries of a single network, never routed across internetwork nodes. This property places ARP into the Link Layer. It is encapsulated. REF: http://www.comptechdoc.org/independent/networking/guide/netarp.html.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Hardware_Addr_Type" type="PacketObj:IANAHardwareType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Characterizes the type of hardware address specified in an ARP message.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Proto_Addr_Type" type="PacketObj:IANAEtherType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>ProtoAddrType characterizes the type of protocol address being mapped. For IPv4 addresses, value = 0x0800.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Hardware_Addr_Size" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Harware_Addr_Size represents the byte size of the hardware address. For Ethernet or other IEEE 802 MAC addresses, the value is 6.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Proto_Addr_Size" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Proto_Addr_Size represents the byte size of the protocol address. IPv4 addresses = 4.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Op_Type" type="PacketObj:ARPOpType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Op_Type characterizes the type of operation. 1 = ARP request, 2=ARP reply, 3=RARP request, 4=RARP reply.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Sender_Hardware_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Sender_Hardware_Addr characterizes the sender's hardware address (e.g., MAC address).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Sender_Protocol_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Sender_Protocol_Addr characterizes the sender's IP address.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Recip_Hardware_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Recip_Sender_Hardware Addr characterizes the recipients' hardware address (e.g., MAC address).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Recip_Protocol_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Recip Protocol Addr characterizes the recipient's IP address.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:IANAHardwareType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
IANAHardwareType specifies the type of hardware, via a union of the IANAHardwareTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IANAHardwareType_datatype
Type restriction of BaseObjectPropertyType
Type hierarchy
Used by
Source
 
<xs:complexType name="IANAHardwareType">
  <xs:annotation>
    <xs:documentation>IANAHardwareType specifies the type of hardware, via a union of the IANAHardwareTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:restriction base="cyboxCommon:BaseObjectPropertyType">
      <xs:simpleType>
        <xs:union memberTypes="PacketObj:IANAHardwareTypeEnum xs:string"/>
      </xs:simpleType>
      <xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
        <xs:annotation>
          <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
  </xs:simpleContent>
</xs:complexType>
Complex Type PacketObj:ARPOpType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ARPOpType specifies types of ARP operations, via a union of the ARPOpTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ARPOpType_datatype
Type restriction of BaseObjectPropertyType
Type hierarchy
Used by
Source
 
<xs:complexType name="ARPOpType">
  <xs:annotation>
    <xs:documentation>ARPOpType specifies types of ARP operations, via a union of the ARPOpTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:restriction base="cyboxCommon:BaseObjectPropertyType">
      <xs:simpleType>
        <xs:union memberTypes="PacketObj:ARPOpTypeEnum xs:string"/>
      </xs:simpleType>
      <xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
        <xs:annotation>
          <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
  </xs:simpleContent>
</xs:complexType>
Complex Type PacketObj:NDPType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
NDP Type characterizes NDP (Neighbor Discover Protocol) IPv6 packets. NDP defines five ICMPv6 packet types. RFC 2461: http://tools.ietf.org/html/rfc4861.
Diagram
Diagram Network_Packet_Object_xsd.tmp#NDPType_ICMPv6_Header Network_Packet_Object_xsd.tmp#NDPType_Router_Solicitation Network_Packet_Object_xsd.tmp#NDPType_Router_Advertisement Network_Packet_Object_xsd.tmp#NDPType_Neighbor_Solicitation Network_Packet_Object_xsd.tmp#NDPType_Neighbor_Advertisement Network_Packet_Object_xsd.tmp#NDPType_Redirect
Used by
Children PacketObj:ICMPv6_Header, PacketObj:Neighbor_Advertisement, PacketObj:Neighbor_Solicitation, PacketObj:Redirect, PacketObj:Router_Advertisement, PacketObj:Router_Solicitation
Source
 
<xs:complexType name="NDPType">
  <xs:annotation>
    <xs:documentation>NDP Type characterizes NDP (Neighbor Discover Protocol) IPv6 packets. NDP defines five ICMPv6 packet types. RFC 2461: http://tools.ietf.org/html/rfc4861.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:annotation>
      <xs:documentation/>
    </xs:annotation>
    <xs:element name="ICMPv6_Header" type="PacketObj:ICMPv6HeaderType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>ICMPv6 Header characterizes an ICMPv6 header.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:choice minOccurs="0">
      <xs:element name="Router_Solicitation" type="PacketObj:RouterSolicitationType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Hosts send Router Solicitations in order to prompt routers to generate Router Advertisements quickly (type=133; code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Router_Advertisement" type="PacketObj:RouterAdvertisementType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Routers send out Router Advertisement messages periodically, or in response to Router Solicitations (type=134; code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Neighbor_Solicitation" type="PacketObj:NeighborSolicitationType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Nodes send Neighbor Solicitations to request the link-layer address of a target node while also providing their own link-layer address to the target. Neighbor Solicitations are multicast when the node needs to resolve an address and unicast when the node seeks to verify the reachability of a neighbor (type=135; code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Neighbor_Advertisement" type="PacketObj:NeighborAdvertisementType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>A node sends Neighbor Advertisements in response to Neighbor Solicitations and sends unsolicited Neighbor Advertisements in order to (unreliably) propagate new information quickly (type=136; code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Redirect" type="PacketObj:RedirectType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Routers send Redirect packets to inform a host of a better first-hop node on the path to a destination. Hosts can be redirected to a better first-hop router but can also be informed by a redirect that the destination is in fact a neighbor. The latter is accomplished by setting the ICMP Target Address equal to the ICMP Destination Address (type=137; code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv6HeaderType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Actual ICMP header bytes are defined, corresponding to the ICMP type, ICMP code, and to the checksum. Translation of each type and code byte are defined in text by using boolean values associated with corresponding elements in the informational and error message type elements.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6HeaderType_Type Network_Packet_Object_xsd.tmp#ICMPv6HeaderType_Code Network_Packet_Object_xsd.tmp#ICMPv6HeaderType_Checksum
Used by
Children PacketObj:Checksum, PacketObj:Code, PacketObj:Type
Source
 
<xs:complexType name="ICMPv6HeaderType">
  <xs:annotation>
    <xs:documentation>Actual ICMP header bytes are defined, corresponding to the ICMP type, ICMP code, and to the checksum. Translation of each type and code byte are defined in text by using boolean values associated with corresponding elements in the informational and error message type elements.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Type" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The ICMP v6 type byte specifies the type of the message. Values range from 0 to 127 (high order bit is 0) indicate an error messages; values from 128 to 255 (high order bit is 1) indicate an informational message.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Code" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The code byte value depends on the message type and provides an additional level of message granularity.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Checksum" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Checksum characterizes the checksum information of an ICMPv6 header.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:RouterSolicitationType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Hosts send Router Solicitations in order to prompt routers to generate Router Advertisements quickly.(type=133; code=0).
Diagram
Diagram Network_Packet_Object_xsd.tmp#RouterSolicitationType_Options
Used by
Children PacketObj:Options
Source
 
<xs:complexType name="RouterSolicitationType">
  <xs:annotation>
    <xs:documentation>Hosts send Router Solicitations in order to prompt routers to generate Router Advertisements quickly.(type=133; code=0).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Options" type="PacketObj:RouterSolicitationOptionsType" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Router Solicitation messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:RouterSolicitationOptionsType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Neighbor Discovery messages include zero or more options, some of which may appear multiple times in the same message.
Diagram
Diagram Network_Packet_Object_xsd.tmp#RouterSolicitationOptionsType_Src_Link_Addr
Used by
Children PacketObj:Src_Link_Addr
Source
 
<xs:complexType name="RouterSolicitationOptionsType">
  <xs:annotation>
    <xs:documentation>Neighbor Discovery messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="Src_Link_Addr" type="PacketObj:NDPLinkAddrType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Src Link Addr characterizes the Source Link-Layer Address option.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:NDPLinkAddrType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
NDPLinkAddrType characterizes the Link-Layer Address option.
Diagram
Diagram Network_Packet_Object_xsd.tmp#NDPLinkAddrType_Length Network_Packet_Object_xsd.tmp#NDPLinkAddrType_Link_Layer_MAC_Addr
Used by
Children PacketObj:Length, PacketObj:Link_Layer_MAC_Addr
Source
 
<xs:complexType name="NDPLinkAddrType">
  <xs:annotation>
    <xs:documentation>NDPLinkAddrType characterizes the Link-Layer Address option.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The length of the option (including the type and length fields) in units of 8 octets.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Link_Layer_MAC_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The variable length link-layer address. The content and format of this field (including byte and bit ordering) is expected to be specified in specific documents that describe how IPv6 operates over different link layers.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:RouterAdvertisementType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Routers send out Router Advertisement messages periodically, or in response to Router Solicitations. (type=134; code=0).
Diagram
Diagram Network_Packet_Object_xsd.tmp#RouterAdvertisementType_managed_address_config_flag Network_Packet_Object_xsd.tmp#RouterAdvertisementType_other_config_flag Network_Packet_Object_xsd.tmp#RouterAdvertisementType_Cur_Hop_Limit Network_Packet_Object_xsd.tmp#RouterAdvertisementType_Router_Lifetime Network_Packet_Object_xsd.tmp#RouterAdvertisementType_Reachable_Time Network_Packet_Object_xsd.tmp#RouterAdvertisementType_Retrans_Timer Network_Packet_Object_xsd.tmp#RouterAdvertisementType_Options
Used by
Children PacketObj:Cur_Hop_Limit, PacketObj:Options, PacketObj:Reachable_Time, PacketObj:Retrans_Timer, PacketObj:Router_Lifetime
Attributes
QName Type Use Annotation
managed_address_config_flag xs:boolean optional 
1-bit "Managed address configuration" flag. When set, it indicates that addresses are available via Dynamic Host Configuration Protocol. If the M flag is set, the O flag is redundant and can be ignored because DHCPv6 will return all available configuration information.
other_config_flag xs:boolean optional 
1-bit "Other configuration" flag. When set, it indicates that other configuration information is available via DHCPv6. Examples of such information are DNS-related information or information on other servers within the network.
Source
 
<xs:complexType name="RouterAdvertisementType">
  <xs:annotation>
    <xs:documentation>Routers send out Router Advertisement messages periodically, or in response to Router Solicitations. (type=134; code=0).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Cur_Hop_Limit" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>8-bit unsigned integer. The default value that should be placed in the Hop Count field of the IP header for outgoing IP packets. A value of zero means unspecified (by this router).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Router_Lifetime" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>16-bit unsigned integer. The lifetime associated with the default router in units of seconds. The field can contain values up to 65535 and receivers should handle any value, while the sending rules in Section 6 limit the lifetime to 9000 seconds.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Reachable_Time" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>32-bit unsigned integer. The time, in milliseconds, between retransmitted Neighbor Solicitation messages. Used by address resolution and the Neighbor Unreachability Detection algorithm. A value of zero means unspecified (by this router).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Retrans_Timer" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>32-bit unsigned integer. The time, in milliseconds, between retransmitted Neighbor Solicitation messages. Used by address resolution and the Neighbor Unreachability Detection algorithm. A value of zero means unspecified (by this router).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Options" type="PacketObj:RouterAdvertisementOptionsType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Neighbor Discovery messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="managed_address_config_flag" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>1-bit "Managed address configuration" flag. When set, it indicates that addresses are available via Dynamic Host Configuration Protocol. If the M flag is set, the O flag is redundant and can be ignored because DHCPv6 will return all available configuration information.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="other_config_flag" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>1-bit "Other configuration" flag. When set, it indicates that other configuration information is available via DHCPv6. Examples of such information are DNS-related information or information on other servers within the network.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>
Complex Type PacketObj:RouterAdvertisementOptionsType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Router Advertisement messages include zero or more options, some of which may appear multiple times in the same message.
Diagram
Diagram Network_Packet_Object_xsd.tmp#RouterAdvertisementOptionsType_Src_Link_Addr Network_Packet_Object_xsd.tmp#RouterAdvertisementOptionsType_MTU Network_Packet_Object_xsd.tmp#RouterAdvertisementOptionsType_Prefix_Info
Used by
Children PacketObj:MTU, PacketObj:Prefix_Info, PacketObj:Src_Link_Addr
Source
 
<xs:complexType name="RouterAdvertisementOptionsType">
  <xs:annotation>
    <xs:documentation>Router Advertisement messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="Src_Link_Addr" type="PacketObj:NDPLinkAddrType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Src Link Addr characterizes the Source Link-Layer Address option.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="MTU" type="PacketObj:NDPMTUType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>32-bit unsigned integer. The recommended MTU for the link.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Prefix_Info" type="PacketObj:NDPPrefixInfoType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Prefix Info characterizes Prefix Information for Router Advertisement Options.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:NDPMTUType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The MTU option is used in Router Advertisement messages to ensure that all nodes on a link use the same MTU value in those cases where the link MTU is not well known. (type=5).
Diagram
Diagram Network_Packet_Object_xsd.tmp#NDPMTUType_Length Network_Packet_Object_xsd.tmp#NDPMTUType_MTU
Used by
Children PacketObj:Length, PacketObj:MTU
Source
 
<xs:complexType name="NDPMTUType">
  <xs:annotation>
    <xs:documentation>The MTU option is used in Router Advertisement messages to ensure that all nodes on a link use the same MTU value in those cases where the link MTU is not well known. (type=5).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The length of the MTU option type: length=1.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="MTU" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The recommended MTU for the link. 32-bit unsigned integer.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:NDPPrefixInfoType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Prefix Info characterizes Prefix Information for Router Advertisement Options. It provides hosts with on-link prefixes and prefixes for Address Autoconfiguration. (type=3). RFC 4861.
Diagram
Diagram Network_Packet_Object_xsd.tmp#NDPPrefixInfoType_link_flag Network_Packet_Object_xsd.tmp#NDPPrefixInfoType_addr_config_flag Network_Packet_Object_xsd.tmp#NDPPrefixInfoType_Length Network_Packet_Object_xsd.tmp#NDPPrefixInfoType_Prefix_Length Network_Packet_Object_xsd.tmp#NDPPrefixInfoType_Valid_Lifetime Network_Packet_Object_xsd.tmp#NDPPrefixInfoType_Preferred_Lifetime Network_Packet_Object_xsd.tmp#NDPPrefixInfoType_Prefix
Used by
Children PacketObj:Length, PacketObj:Preferred_Lifetime, PacketObj:Prefix, PacketObj:Prefix_Length, PacketObj:Valid_Lifetime
Attributes
QName Type Use Annotation
addr_config_flag xs:boolean optional 
1-bit autonomous address-configuration flag. When set indicates that this prefix can be usd for stateless address configuration.
link_flag xs:boolean optional 
1-bit on-link flag. When set, indicates that this prefix can be used for on-link determintation. When not set the advertisement makes no statement about on-link or off-link properties of the prefix.
Source
 
<xs:complexType name="NDPPrefixInfoType">
  <xs:annotation>
    <xs:documentation>Prefix Info characterizes Prefix Information for Router Advertisement Options. It provides hosts with on-link prefixes and prefixes for Address Autoconfiguration. (type=3). RFC 4861.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Length characterizes the length of the option (the number of valid leading bits in the prefix), and is represented as a 32-bit integer.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Prefix_Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>8-bit unsigned integer. The number of leading bits in the Prefix that are valid. The value ranges from 0 to 128. The prefix length field provides necessary information for on-link determination (when combined with the L flag in the prefix information option).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Valid_Lifetime" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>32-bit unsigned integer. The length of time in seconds (relative to the time the packet is sent) that the prefix is valid for the purpose of on-link determination. A value of all one bits (0xffffffff) represents infinity.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Preferred_Lifetime" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>32-bit unsigned integer. The length of time in seconds (relative to the time the packet is sent) that addresses generated from the prefix via stateless address autoconfiguration remain preferred.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Prefix" type="PacketObj:PrefixType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The Prefix is an IP address or a prefix of an IP address.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="link_flag" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>1-bit on-link flag. When set, indicates that this prefix can be used for on-link determintation. When not set the advertisement makes no statement about on-link or off-link properties of the prefix.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="addr_config_flag" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>1-bit autonomous address-configuration flag. When set indicates that this prefix can be usd for stateless address configuration.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>
Complex Type PacketObj:PrefixType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Provides an IP address or a prefix of an IP address for NDP for IPv6.
Diagram
Diagram Network_Packet_Object_xsd.tmp#PrefixType_IPv6_Addr Network_Packet_Object_xsd.tmp#PrefixType_IP_Addr_Prefix
Used by
Children PacketObj:IP_Addr_Prefix, PacketObj:IPv6_Addr
Source
 
<xs:complexType name="PrefixType">
  <xs:annotation>
    <xs:documentation>Provides an IP address or a prefix of an IP address for NDP for IPv6.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="IPv6_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>IPv6 address.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="IP_Addr_Prefix" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The initial bits of an IPv6 address (these are identical for all hosts in a network) form the network's prefix. http://ipv6.com/articles/general/IPv6-Addressing.htm.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:NeighborSolicitationType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Nodes send Neighbor Solicitations to request the link-layer address of a target node while also providing their own link-layer address to the target. Neighbor Solicitations are multicast when the node needs to resolve an address and unicast when the node seeks to verify the reachability of a neighbor. (type=135; code=0).
Diagram
Diagram Network_Packet_Object_xsd.tmp#NeighborSolicitationType_Target_IPv6_Addr Network_Packet_Object_xsd.tmp#NeighborSolicitationType_Options
Used by
Children PacketObj:Options, PacketObj:Target_IPv6_Addr
Source
 
<xs:complexType name="NeighborSolicitationType">
  <xs:annotation>
    <xs:documentation>Nodes send Neighbor Solicitations to request the link-layer address of a target node while also providing their own link-layer address to the target. Neighbor Solicitations are multicast when the node needs to resolve an address and unicast when the node seeks to verify the reachability of a neighbor. (type=135; code=0).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Target_IPv6_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The IP address of the target of the solicitation.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Options" type="PacketObj:NeighborSolicitationOptionsType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Neighbor Solicitation messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:NeighborSolicitationOptionsType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Neighbor Solicitation messages include zero or more options, some of which may appear multiple times in the same message.
Diagram
Diagram Network_Packet_Object_xsd.tmp#NeighborSolicitationOptionsType_Src_Link_Addr
Used by
Children PacketObj:Src_Link_Addr
Source
 
<xs:complexType name="NeighborSolicitationOptionsType">
  <xs:annotation>
    <xs:documentation>Neighbor Solicitation messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="Src_Link_Addr" type="PacketObj:NDPLinkAddrType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Src Link Addr characterizes the Source Link-Layer Address option.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:NeighborAdvertisementType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
A node sends Neighbor Advertisements in response to Neighbor Solicitations and sends unsolicited Neighbor Advertisements in order to (unreliably) propagate new information quickly. (type=136; code=0).
Diagram
Diagram Network_Packet_Object_xsd.tmp#NeighborAdvertisementType_router_flag Network_Packet_Object_xsd.tmp#NeighborAdvertisementType_solicited_flag Network_Packet_Object_xsd.tmp#NeighborAdvertisementType_override_flag Network_Packet_Object_xsd.tmp#NeighborAdvertisementType_Target_IPv6_Addr Network_Packet_Object_xsd.tmp#NeighborAdvertisementType_Options
Used by
Children PacketObj:Options, PacketObj:Target_IPv6_Addr
Attributes
QName Type Use Annotation
override_flag xs:boolean optional 
Override flag. When set, the O-bit indicates that the advertisement should override an existing cache entry and update the cached link-layer address.
router_flag xs:boolean optional 
Router flag. When set, the R-bit indicates that the sender is a router. The R-bit is used by Neighbor Unreachability Detection to detect a router that changes to a host.
solicited_flag xs:boolean optional 
Solicited flag. When set, the S-bit indicates that the advertisement was sent in response to a Neighbor Solicitation from the Destination address. The S-bit is used as a reachability confirmation for Neighbor Unreachability Detection.
Source
 
<xs:complexType name="NeighborAdvertisementType">
  <xs:annotation>
    <xs:documentation>A node sends Neighbor Advertisements in response to Neighbor Solicitations and sends unsolicited Neighbor Advertisements in order to (unreliably) propagate new information quickly. (type=136; code=0).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Target_IPv6_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The IP address of the target of the advertisement.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Options" type="PacketObj:NeighborOptionsType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Neighbor Advertisement messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="router_flag" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>Router flag. When set, the R-bit indicates that the sender is a router. The R-bit is used by Neighbor Unreachability Detection to detect a router that changes to a host.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="solicited_flag" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>Solicited flag. When set, the S-bit indicates that the advertisement was sent in response to a Neighbor Solicitation from the Destination address. The S-bit is used as a reachability confirmation for Neighbor Unreachability Detection.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="override_flag" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>Override flag. When set, the O-bit indicates that the advertisement should override an existing cache entry and update the cached link-layer address.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>
Complex Type PacketObj:NeighborOptionsType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Neighbor Advertisement messages include zero or more options, some of which may appear multiple times in the same message.
Diagram
Diagram Network_Packet_Object_xsd.tmp#NeighborOptionsType_Target_Link_Addr
Used by
Children PacketObj:Target_Link_Addr
Source
 
<xs:complexType name="NeighborOptionsType">
  <xs:annotation>
    <xs:documentation>Neighbor Advertisement messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="Target_Link_Addr" type="PacketObj:NDPLinkAddrType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Target Link Addr characterizes the Target Link-Layer Address option.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:RedirectType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Routers send Redirect packets to inform a host of a better first-hop node on the path to a destination. Hosts can be redirected to a better first-hop router but can also be informed by a redirect that the destination is in fact a neighbor. The latter is accomplished by setting the ICMP Target Address equal to the ICMP Destination Address. (type=137; code=0).
Diagram
Diagram Network_Packet_Object_xsd.tmp#RedirectType_Target_IPv6_Addr Network_Packet_Object_xsd.tmp#RedirectType_Dest_IPv6_Addr Network_Packet_Object_xsd.tmp#RedirectType_Options
Used by
Children PacketObj:Dest_IPv6_Addr, PacketObj:Options, PacketObj:Target_IPv6_Addr
Source
 
<xs:complexType name="RedirectType">
  <xs:annotation>
    <xs:documentation>Routers send Redirect packets to inform a host of a better first-hop node on the path to a destination. Hosts can be redirected to a better first-hop router but can also be informed by a redirect that the destination is in fact a neighbor. The latter is accomplished by setting the ICMP Target Address equal to the ICMP Destination Address. (type=137; code=0).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Target_IPv6_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>An IP address that is a better first hop to use for the ICMP Destination Address.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Dest_IPv6_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The IP address of the destination that is redirected to the target.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Options" type="PacketObj:RedirectOptionsType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Redirect messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:RedirectOptionsType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Redirect messages include zero or more options, some of which may appear multiple times in the same message.
Diagram
Diagram Network_Packet_Object_xsd.tmp#RedirectOptionsType_Target_Link_Addr Network_Packet_Object_xsd.tmp#RedirectOptionsType_Redirected_Header
Used by
Children PacketObj:Redirected_Header, PacketObj:Target_Link_Addr
Source
 
<xs:complexType name="RedirectOptionsType">
  <xs:annotation>
    <xs:documentation>Redirect messages include zero or more options, some of which may appear multiple times in the same message.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="Target_Link_Addr" type="PacketObj:NDPLinkAddrType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The link-layer address for the target.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Redirected_Header" type="PacketObj:NDPRedirectedHeaderType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>As much as possible of the IP packet that triggered the sending of the Redirect message without making the redirect packet exceed the minimum MTU specified in the IPv6 protocol.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:NDPRedirectedHeaderType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The redirected header option is used in redirect messages and contains all or part of the packet that is being redirected. (type=4).
Diagram
Diagram Network_Packet_Object_xsd.tmp#NDPRedirectedHeaderType_Length Network_Packet_Object_xsd.tmp#NDPRedirectedHeaderType_IPHeader_And_Data
Used by
Children PacketObj:IPHeader_And_Data, PacketObj:Length
Source
 
<xs:complexType name="NDPRedirectedHeaderType">
  <xs:annotation>
    <xs:documentation>The redirected header option is used in redirect messages and contains all or part of the packet that is being redirected. (type=4).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The length of the option (including the type and length fields) in units of 8 octets.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="IPHeader_And_Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>As much as possible of the IP packet that triggered the sending of the redirect without making redirect packet larger than MTU.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:InternetLayerType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Internet layer is the group of methods, protocols, and specifications that are used to transport packets from the originating host across network boundaries. Not all protocols are currently defined, just those most commonly used: IPv4, ICMPv4, IPv6, ICMPv6. Other protocols will be added as needed. (http://en.wikipedia.org/wiki/Internet_layer).
Diagram
Diagram Network_Packet_Object_xsd.tmp#InternetLayerType_IPv4 Network_Packet_Object_xsd.tmp#InternetLayerType_ICMPv4 Network_Packet_Object_xsd.tmp#InternetLayerType_IPv6 Network_Packet_Object_xsd.tmp#InternetLayerType_ICMPv6
Used by
Children PacketObj:ICMPv4, PacketObj:ICMPv6, PacketObj:IPv4, PacketObj:IPv6
Source
 
<xs:complexType name="InternetLayerType">
  <xs:annotation>
    <xs:documentation>The Internet layer is the group of methods, protocols, and specifications that are used to transport packets from the originating host across network boundaries. Not all protocols are currently defined, just those most commonly used: IPv4, ICMPv4, IPv6, ICMPv6. Other protocols will be added as needed. (http://en.wikipedia.org/wiki/Internet_layer).</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="IPv4" type="PacketObj:IPv4PacketType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Internet Protocol version 4 (IPv4) is a connectionless protocol for use on packet-switched link layer networks (e.g., Ethernet).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="ICMPv4" type="PacketObj:ICMPv4PacketType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>ICMP is chiefly used the operating systems of networked computers to send error messages indicating, for example, that a requested service is not available or that a host or router could not be reached (http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol; REF: http://www.networksorcery.com/enp/protocol/icmp.htm).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="IPv6" type="PacketObj:IPv6PacketType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Internet Protocol version 6 (IPv6) is intended to succeed IPv4, and like IPv4 it is a connectionless protocol for use on packet-switched link layer networks.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="ICMPv6" type="PacketObj:ICMPv6PacketType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>ICMPv6 is the implementation of the ICMP for IPv6. ICMPv6 performs error reporting and diagnostic functions.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:IPv4PacketType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Internet Protocol version 4 (IPv4) is a connectionless protocol for use on packet-switched link layer networks (e.g., Ethernet). REF: RFC 791; http://en.wikipedia.org/wiki/IPv4.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4PacketType_IPv4_Header Network_Packet_Object_xsd.tmp#IPv4PacketType_Data
Used by
Children PacketObj:Data, PacketObj:IPv4_Header
Source
 
<xs:complexType name="IPv4PacketType">
  <xs:annotation>
    <xs:documentation>Internet Protocol version 4 (IPv4) is a connectionless protocol for use on packet-switched link layer networks (e.g., Ethernet). REF: RFC 791; http://en.wikipedia.org/wiki/IPv4.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="IPv4_Header" type="PacketObj:IPv4HeaderType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The IPv4 header provides addressing, and internet modules use fields in the header to fragment and reassemble internet datagrams when necessary for transmission through small packet networks.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The data portion of an IP packet is interpreted based on the value of the Protocol header field. Actual field values will probably be specified in the elements of the different network layers, but we provide a field here to capture any data as necessary.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:IPv4HeaderType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The IPv4 header provides addressing, and internet modules use fields in the header to fragment and reassemble internet datagrams when necessary for transmission through small packet networks. REF: RFC 791.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4HeaderType_IP_Version Network_Packet_Object_xsd.tmp#IPv4HeaderType_Header_Length Network_Packet_Object_xsd.tmp#IPv4HeaderType_DSCP Network_Packet_Object_xsd.tmp#IPv4HeaderType_ECN Network_Packet_Object_xsd.tmp#IPv4HeaderType_Total_Length Network_Packet_Object_xsd.tmp#IPv4HeaderType_Identification Network_Packet_Object_xsd.tmp#IPv4HeaderType_Flags Network_Packet_Object_xsd.tmp#IPv4HeaderType_Fragment_Offset Network_Packet_Object_xsd.tmp#IPv4HeaderType_TTL Network_Packet_Object_xsd.tmp#IPv4HeaderType_Protocol Network_Packet_Object_xsd.tmp#IPv4HeaderType_Checksum Network_Packet_Object_xsd.tmp#IPv4HeaderType_Src_IPv4_Addr Network_Packet_Object_xsd.tmp#IPv4HeaderType_Dest_IPv4_Addr Network_Packet_Object_xsd.tmp#IPv4HeaderType_Option
Used by
Children PacketObj:Checksum, PacketObj:DSCP, PacketObj:Dest_IPv4_Addr, PacketObj:ECN, PacketObj:Flags, PacketObj:Fragment_Offset, PacketObj:Header_Length, PacketObj:IP_Version, PacketObj:Identification, PacketObj:Option, PacketObj:Protocol, PacketObj:Src_IPv4_Addr, PacketObj:TTL, PacketObj:Total_Length
Source
 
<xs:complexType name="IPv4HeaderType">
  <xs:annotation>
    <xs:documentation>The IPv4 header provides addressing, and internet modules use fields in the header to fragment and reassemble internet datagrams when necessary for transmission through small packet networks. REF: RFC 791.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="IP_Version" type="PacketObj:IPVersionType" fixed="IPv4(4)" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The version field indicates the format of the internet header. For IP v4, the version is 4.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Header_Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The Internet Header Length specifies the length of IP packet header in 32 bit words. Min value = 5.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="DSCP" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Originally defined as the Type of Service field, the Differentiated Services Code Point (DSCP) field is now defined by RFC 2474 for Differentiated services (DiffServ). New technologies are emerging that require real-time data streaming and therefore make use of the DSCP field. An example is Voice over IP (VoIP), which is used for interactive data voice exchange (http://en.wikipedia.org/wiki/IPv4).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="ECN" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Explicit Congestion Notification: This field is defined in RFC 3168 and allows end-to-end notification of network congestion without dropping packets. ECN is an optional feature that is only used when both endpoints support it and are willing to use it. It is only effective when supported by the underlying network. (http://en.wikipedia.org/wiki/IPv4).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Total_Length" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This 16-bit field defines the entire datagram size, including header and data, in bytes.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Identification" type="cyboxCommon:PositiveIntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The Identification field is primarily used for uniquely identifying fragments of an original IP datagram. (http://en.wikipedia.org/wiki/IPv4).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Flags" type="PacketObj:IPv4FlagsType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This is a three-bit field used to control or identify fragments. An field has been defined for each bit with associated enumerated types.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Fragment_Offset" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The fragment offset field is 13 bits long and specifies the offset of a particular fragment relative to the beginning of the original unfragmented IP datagram. http://en.wikipedia.org/wiki/IPv4.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="TTL" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This 8-bit field helps prevent datagrams from persisting on an internet (it limits a datagram's lifetime).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Protocol" type="PacketObj:IANAAssignedIPNumbersType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field defines the protocol used in the data portion of the IP datagram. The type of this field is an enumerated list of IP protocol numbers as maintained by the Internet Assigned Numbers Authority.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Checksum" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field is a 16-bit checksum used for error-checking of the header.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Src_IPv4_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field is the IPv4 address of the sender of the packet.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Dest_IPv4_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field is the IPv4 address of the receiver of the packet.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:sequence minOccurs="0">
      <xs:element name="Option" type="PacketObj:IPv4OptionType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>The IPv4 option field is variable in length with zero or more options. It is not often used. http://en.wikipedia.org/wiki/IPv4.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:IPVersionType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
IPVersionType specifies IP versions, via a union of the IPVersionTypeEnum type and the atomic xs:string type. See http://www.iana.org/assignments/version-numbers/version-numbers.xml for a complete list. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPVersionType_datatype
Type restriction of BaseObjectPropertyType
Type hierarchy
Used by
Source
 
<xs:complexType name="IPVersionType">
  <xs:annotation>
    <xs:documentation>IPVersionType specifies IP versions, via a union of the IPVersionTypeEnum type and the atomic xs:string type. See http://www.iana.org/assignments/version-numbers/version-numbers.xml for a complete list. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:restriction base="cyboxCommon:BaseObjectPropertyType">
      <xs:simpleType>
        <xs:union memberTypes="PacketObj:IPVersionTypeEnum xs:string"/>
      </xs:simpleType>
      <xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
        <xs:annotation>
          <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
  </xs:simpleContent>
</xs:complexType>
Complex Type PacketObj:IPv4FlagsType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
These flag types are used to control or identify fragments in an IP packet. It is a three-bit field, each of the three bits are defined by a field with a string value that indicates the meaning of whether or not the bit is set.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4FlagsType_Reserved Network_Packet_Object_xsd.tmp#IPv4FlagsType_Do_Not_Fragment Network_Packet_Object_xsd.tmp#IPv4FlagsType_More_Fragments
Used by
Children PacketObj:Do_Not_Fragment, PacketObj:More_Fragments, PacketObj:Reserved
Source
 
<xs:complexType name="IPv4FlagsType">
  <xs:annotation>
    <xs:documentation>These flag types are used to control or identify fragments in an IP packet. It is a three-bit field, each of the three bits are defined by a field with a string value that indicates the meaning of whether or not the bit is set.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Reserved" type="cyboxCommon:IntegerObjectPropertyType" fixed="0" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Bit 0: This bit value (0) is reserved and must be zero.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Do_Not_Fragment" type="PacketObj:DoNotFragmentType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Bit 1: This is the "don't fragment" bit. Values are specified in the DoNotFragmentType.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="More_Fragments" type="PacketObj:MoreFragmentsType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Bit 2: This is the "more fragments" bit. Values are specified in the MoreFragmentsType.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:DoNotFragmentType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
DoNotFragmentType specifies fragmenting options, via a union of the DoNotFragmentTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.
Diagram
Diagram Network_Packet_Object_xsd.tmp#DoNotFragmentType_datatype
Type restriction of BaseObjectPropertyType
Type hierarchy
Used by
Source
 
<xs:complexType name="DoNotFragmentType">
  <xs:annotation>
    <xs:documentation>DoNotFragmentType specifies fragmenting options, via a union of the DoNotFragmentTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:restriction base="cyboxCommon:BaseObjectPropertyType">
      <xs:simpleType>
        <xs:union memberTypes="PacketObj:DoNotFragmentTypeEnum xs:string"/>
      </xs:simpleType>
      <xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
        <xs:annotation>
          <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
  </xs:simpleContent>
</xs:complexType>
Complex Type PacketObj:MoreFragmentsType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
MoreFragmentsType specifies whether there are more fragments, via a union of the MoreFragmentsTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.
Diagram
Diagram Network_Packet_Object_xsd.tmp#MoreFragmentsType_datatype
Type restriction of BaseObjectPropertyType
Type hierarchy
Used by
Source
 
<xs:complexType name="MoreFragmentsType">
  <xs:annotation>
    <xs:documentation>MoreFragmentsType specifies whether there are more fragments, via a union of the MoreFragmentsTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:restriction base="cyboxCommon:BaseObjectPropertyType">
      <xs:simpleType>
        <xs:union memberTypes="PacketObj:MoreFragmentsTypeEnum xs:string"/>
      </xs:simpleType>
      <xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
        <xs:annotation>
          <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
  </xs:simpleContent>
</xs:complexType>
Complex Type PacketObj:IANAAssignedIPNumbersType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
IANAAssignedIPNumbersType specifies Internet Protocol numbers, via a union of the IANAAssignedIPNumbersTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IANAAssignedIPNumbersType_datatype
Type restriction of BaseObjectPropertyType
Type hierarchy
Used by
Source
 
<xs:complexType name="IANAAssignedIPNumbersType">
  <xs:annotation>
    <xs:documentation>IANAAssignedIPNumbersType specifies Internet Protocol numbers, via a union of the IANAAssignedIPNumbersTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:restriction base="cyboxCommon:BaseObjectPropertyType">
      <xs:simpleType>
        <xs:union memberTypes="PacketObj:IANAAssignedIPNumbersTypeEnum xs:string"/>
      </xs:simpleType>
      <xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
        <xs:annotation>
          <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
  </xs:simpleContent>
</xs:complexType>
Complex Type PacketObj:IPv4OptionType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The IPv4 option field is variable in length with zero or more options.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4OptionType_Copy_Flag Network_Packet_Object_xsd.tmp#IPv4OptionType_Class Network_Packet_Object_xsd.tmp#IPv4OptionType_Option
Used by
Children PacketObj:Class, PacketObj:Copy_Flag, PacketObj:Option
Source
 
<xs:complexType name="IPv4OptionType">
  <xs:annotation>
    <xs:documentation>The IPv4 option field is variable in length with zero or more options.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Copy_Flag" type="PacketObj:IPv4CopyFlagType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The copied flag indicates that this option is copied into all fragments on fragmentation. 1 bit. They are represented in this field by a string which specifies their value.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Class" type="PacketObj:IPv4ClassType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The option class is represented by 2 bits where 0 = control; 1 = reserved for future use; 2 = debugging and measurement; 3 = reserved for future use. These enumerated values are defined for this field.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Option" type="PacketObj:IPv4OptionsType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The Internet Protocol has provision for optional header fields identified by an option type. These types are enumerated in the IPv4OptionsType.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:IPv4CopyFlagType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
IPv4CopyFlagType specifies value of IPv4 copy flag, via a union of the IPv4CopyFlagTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4CopyFlagType_datatype
Type restriction of BaseObjectPropertyType
Type hierarchy
Used by
Source
 
<xs:complexType name="IPv4CopyFlagType">
  <xs:annotation>
    <xs:documentation>IPv4CopyFlagType specifies value of IPv4 copy flag, via a union of the IPv4CopyFlagTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:restriction base="cyboxCommon:BaseObjectPropertyType">
      <xs:simpleType>
        <xs:union memberTypes="PacketObj:IPv4CopyFlagTypeEnum xs:string"/>
      </xs:simpleType>
      <xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
        <xs:annotation>
          <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
  </xs:simpleContent>
</xs:complexType>
Complex Type PacketObj:IPv4ClassType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
IPv4ClassType specifies IPv4 class type, via a union of the IPv4ClassTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4ClassType_datatype
Type restriction of BaseObjectPropertyType
Type hierarchy
Used by
Source
 
<xs:complexType name="IPv4ClassType">
  <xs:annotation>
    <xs:documentation>IPv4ClassType specifies IPv4 class type, via a union of the IPv4ClassTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:restriction base="cyboxCommon:BaseObjectPropertyType">
      <xs:simpleType>
        <xs:union memberTypes="PacketObj:IPv4ClassTypeEnum xs:string"/>
      </xs:simpleType>
      <xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
        <xs:annotation>
          <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
  </xs:simpleContent>
</xs:complexType>
Complex Type PacketObj:IPv4OptionsType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
IPv4OptionsType specifies IPv4 options, via a union of the IPv4OptionsTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv4OptionsType_datatype
Type restriction of BaseObjectPropertyType
Type hierarchy
Used by
Source
 
<xs:complexType name="IPv4OptionsType">
  <xs:annotation>
    <xs:documentation>IPv4OptionsType specifies IPv4 options, via a union of the IPv4OptionsTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:restriction base="cyboxCommon:BaseObjectPropertyType">
      <xs:simpleType>
        <xs:union memberTypes="PacketObj:IPv4OptionsTypeEnum xs:string"/>
      </xs:simpleType>
      <xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
        <xs:annotation>
          <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
  </xs:simpleContent>
</xs:complexType>
Complex Type PacketObj:ICMPv4PacketType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ICMP is used to send error messages (e.g., a datagram cannot reach its destination), informational messages ( e.g., timestamp information), or a traceroute message. REF: http://www.networksorcery.com/enp/protocol/icmp.htm.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4PacketType_ICMPv4_Header Network_Packet_Object_xsd.tmp#ICMPv4PacketType_Error_Msg Network_Packet_Object_xsd.tmp#ICMPv4PacketType_Info_Msg Network_Packet_Object_xsd.tmp#ICMPv4PacketType_Traceroute
Used by
Children PacketObj:Error_Msg, PacketObj:ICMPv4_Header, PacketObj:Info_Msg, PacketObj:Traceroute
Source
 
<xs:complexType name="ICMPv4PacketType">
  <xs:annotation>
    <xs:documentation>ICMP is used to send error messages (e.g., a datagram cannot reach its destination), informational messages ( e.g., timestamp information), or a traceroute message. REF: http://www.networksorcery.com/enp/protocol/icmp.htm.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="ICMPv4_Header" type="PacketObj:ICMPv4HeaderType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Actual header bytes are captured here. The message content of each type/code pair is also defined as part of the larger, complex "ICMPv4PacketType" type as either an error message, an informational message, or a traceroute message. The meaning of the type and code bytes is made explicit in the elements corresponding to each message type.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:choice minOccurs="0">
      <xs:annotation>
        <xs:documentation/>
      </xs:annotation>
      <xs:element name="Error_Msg" type="PacketObj:ICMPv4ErrorMessageType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>For ICMP error messages, boolean values are used in this field to explicitly interpret the type and code bytes appearing in the ICMP header. Additional fields and message content are also defined here.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Info_Msg" type="PacketObj:ICMPv4InfoMessageType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>For ICMP informational messages, boolean values are used in this field to explicitly interpret the type and code bytes appearing in the ICMP header. Additional fields and message content are also defined here.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Traceroute" type="PacketObj:ICMPv4TracerouteType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>For ICMP traceroute messages (type = 30), specifies related fields and ICMP code value. A boolean value is used to explicitly interpret the code byte appearing in the ICMP header. Additional fields and message content are also defined here.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv4HeaderType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Actual ICMP header bytes are defined, corresponding to the ICMP type, ICMP code, and to the checksum.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4HeaderType_Type Network_Packet_Object_xsd.tmp#ICMPv4HeaderType_Code Network_Packet_Object_xsd.tmp#ICMPv4HeaderType_Checksum
Used by
Children PacketObj:Checksum, PacketObj:Code, PacketObj:Type
Source
 
<xs:complexType name="ICMPv4HeaderType">
  <xs:annotation>
    <xs:documentation>Actual ICMP header bytes are defined, corresponding to the ICMP type, ICMP code, and to the checksum.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Type" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>ICMP Type byte specifies the format of the ICMP message.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Code" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>ICMP Code byte further qualifies the ICMP message.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Checksum" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>ICMP Checksum (16 bits) covers the ICMP message.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv4ErrorMessageType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ICMP error messages include destination unreachable messages, source quench messages, redirect messages, and time exceeded messages.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageType_Destination_Unreachable Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageType_Source_Quench Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageType_Redirect_Message Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageType_Time_Exceeded Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageType_Error_Msg_Content
Used by
Children PacketObj:Destination_Unreachable, PacketObj:Error_Msg_Content, PacketObj:Redirect_Message, PacketObj:Source_Quench, PacketObj:Time_Exceeded
Source
 
<xs:complexType name="ICMPv4ErrorMessageType">
  <xs:annotation>
    <xs:documentation>ICMP error messages include destination unreachable messages, source quench messages, redirect messages, and time exceeded messages.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Destination_Unreachable" type="PacketObj:ICMPv4DestinationUnreachableType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>A destination unreachable message is an ICMP message which is generated by the host or its inbound gateway to inform the client that the destination is unreachable for some reason (http://en.wikipedia.org/wiki/ICMP_Destination_Unreachable).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Source_Quench" type="PacketObj:ICMPv4SourceQuenchType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>A source quench message is an ICMP message that requests that the sender decrease the rate of messages sent to a router or host. This message may be generated if a router or host does not have sufficient buffer space to process the request or may occur if the router or host buffer is approaching its limit (http://en.wikipedia.org/wiki/ICMP_Source_Quench).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Redirect_Message" type="PacketObj:ICMPv4RedirectMessageType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>A redirect message is used to send data packets on an alternative route. This ICMP redirect message informs a host to update its routing information.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Time_Exceeded" type="PacketObj:ICMPv4TimeExceededType" form="qualified" minOccurs="0">
        <xs:annotation>
          <xs:documentation>An ICMP time exceeded message is generated by a gateway to inform the source of a datagram that the datagram has been discarded due to the time to live field reaching zero. A time exceeded message may also be sent by a host if it fails to reassemble a fragmented datagram within its time limit (http://en.wikipedia.org/wiki/ICMP_Time_Exceeded).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="Error_Msg_Content" type="PacketObj:ICMPv4ErrorMessageContentType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Message content common to all ICMP error messages are defined here. Fields that are specific to individual messages are defined separately under each message type.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv4DestinationUnreachableType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Destination Unreachable error message; ICMP type=3.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Destination_Network_Unreachable Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Destination_Host_Unreachable Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Destination_Protocol_Unreachable Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Destination_Port_Unreachable Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Fragmentation_Required Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Source_Route_Failed Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Destination_Network_Unknown Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Destination_Host_Unknown Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Source_Host_Isolated Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Network_Administratively_Prohibited Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Host_Administratively_Prohibited Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Network_Unreachable_For_TOS Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Host_Unreachable_For_TOS Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Communication_Administratively_Prohibited Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Host_Precedence_Violation Network_Packet_Object_xsd.tmp#ICMPv4DestinationUnreachableType_Precedence_Cutoff_In_Effect
Used by
Children PacketObj:Communication_Administratively_Prohibited, PacketObj:Destination_Host_Unknown, PacketObj:Destination_Host_Unreachable, PacketObj:Destination_Network_Unknown, PacketObj:Destination_Network_Unreachable, PacketObj:Destination_Port_Unreachable, PacketObj:Destination_Protocol_Unreachable, PacketObj:Fragmentation_Required, PacketObj:Host_Administratively_Prohibited, PacketObj:Host_Precedence_Violation, PacketObj:Host_Unreachable_For_TOS, PacketObj:Network_Administratively_Prohibited, PacketObj:Network_Unreachable_For_TOS, PacketObj:Precedence_Cutoff_In_Effect, PacketObj:Source_Host_Isolated, PacketObj:Source_Route_Failed
Source
 
<xs:complexType name="ICMPv4DestinationUnreachableType">
  <xs:annotation>
    <xs:documentation>Destination Unreachable error message; ICMP type=3.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="Destination_Network_Unreachable" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; destination network unreachable (code=0).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Destination_Host_Unreachable" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; destination host unreachable (code=1).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Destination_Protocol_Unreachable" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; destination protocol unreachable (code=2).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Destination_Port_Unreachable" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; destination port unreachable (code=3).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Fragmentation_Required" type="PacketObj:FragmentationRequiredType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; fragmentation required (code=4). This field has an additional field (Next-Hop MTU), as well as a boolean value indicating this subtype.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Source_Route_Failed" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; source route failed (code=5).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Destination_Network_Unknown" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; destination network unknown (code=6).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Destination_Host_Unknown" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; destination host unknown (code=7).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Source_Host_Isolated" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; source host isolated (code=8).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Network_Administratively_Prohibited" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; host administratively prohibited (code=9).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Host_Administratively_Prohibited" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; host administratively prohibited (code=10).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Network_Unreachable_For_TOS" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; network unreachable for TOS (code=11).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Host_Unreachable_For_TOS" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; host unreachable for TOS (code=12).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Communication_Administratively_Prohibited" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; communication administratively prohibited (code=13).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Host_Precedence_Violation" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; host precedence violation (code=14).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Precedence_Cutoff_In_Effect" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>One of 16 different subtypes of a destination unreachable ICMP message; precedence cutoff in effect (code=15).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:FragmentationRequiredType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This further specifies an ICMP destination unreachable (type=3) message of code=4 (fragmentation required) message by providing a Next-Hop MTU field.
Diagram
Diagram Network_Packet_Object_xsd.tmp#FragmentationRequiredType_Fragmentation_Required Network_Packet_Object_xsd.tmp#FragmentationRequiredType_Next_Hop_MTU
Used by
Children PacketObj:Fragmentation_Required, PacketObj:Next_Hop_MTU
Source
 
<xs:complexType name="FragmentationRequiredType">
  <xs:annotation>
    <xs:documentation>This further specifies an ICMP destination unreachable (type=3) message of code=4 (fragmentation required) message by providing a Next-Hop MTU field.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Fragmentation_Required" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Indicates that the subtype of the destination unreachable ICMP message is "fragmentation required".</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Next_Hop_MTU" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The Next-Hop MTU field contains the MTU of the next-hop network is a code 4 error (fragmentation required) occurs.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv4SourceQuenchType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Source Quench (congestion control) error message; ICMP type=4.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4SourceQuenchType_Source_Quench
Used by
Children PacketObj:Source_Quench
Source
 
<xs:complexType name="ICMPv4SourceQuenchType">
  <xs:annotation>
    <xs:documentation>Source Quench (congestion control) error message; ICMP type=4.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="Source_Quench" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Source quench is the only subtype (code=0).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:ICMPv4RedirectMessageType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Redirect Message error message; ICMP type=5.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4RedirectMessageType_Network_Redirect Network_Packet_Object_xsd.tmp#ICMPv4RedirectMessageType_Host_Redirect Network_Packet_Object_xsd.tmp#ICMPv4RedirectMessageType_ToS_Network_Redirect Network_Packet_Object_xsd.tmp#ICMPv4RedirectMessageType_ToS_Host_Redirect Network_Packet_Object_xsd.tmp#ICMPv4RedirectMessageType_IP_Address
Used by
Children PacketObj:Host_Redirect, PacketObj:IP_Address, PacketObj:Network_Redirect, PacketObj:ToS_Host_Redirect, PacketObj:ToS_Network_Redirect
Source
 
<xs:complexType name="ICMPv4RedirectMessageType">
  <xs:annotation>
    <xs:documentation>Redirect Message error message; ICMP type=5.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Network_Redirect" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>One of 4 different subtypes of a redirect ICMP message; redirect datagram for the network (code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Host_Redirect" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>One of 4 different subtypes of a redirect ICMP message; redirect datagram for the host (code=1).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="ToS_Network_Redirect" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>One of 4 different subtypes of a redirect ICMP message; redirect datagram for the TOS and network (code=2).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="ToS_Host_Redirect" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>One of 4 different subtypes of a redirect ICMP message; redirect datagram for the TOS and host (code=3).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="IP_Address" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The IP address is the 32-bit address of the gateway to which the redirection should be sent.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv4TimeExceededType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Time Exceeded error message; ICMP type=11.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4TimeExceededType_TTL_Exceeded_In_Transit Network_Packet_Object_xsd.tmp#ICMPv4TimeExceededType_Frag_Reassembly_Time_Exceeded
Used by
Children PacketObj:Frag_Reassembly_Time_Exceeded, PacketObj:TTL_Exceeded_In_Transit
Source
 
<xs:complexType name="ICMPv4TimeExceededType">
  <xs:annotation>
    <xs:documentation>Time Exceeded error message; ICMP type=11.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="TTL_Exceeded_In_Transit" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>specifies that the time-to-live was exceeded in transit (code=0).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Frag_Reassembly_Time_Exceeded" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>specifies that the fragment reassembly time was exceeded (code=1).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:ICMPv4ErrorMessageContentType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Elements associated with ICMPv4 error messages (as opposed to ICMP informational messages or ICMP traceroute message).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageContentType_IP_Header Network_Packet_Object_xsd.tmp#ICMPv4ErrorMessageContentType_First_Eight_Bytes
Used by
Children PacketObj:First_Eight_Bytes, PacketObj:IP_Header
Source
 
<xs:complexType name="ICMPv4ErrorMessageContentType">
  <xs:annotation>
    <xs:documentation>Elements associated with ICMPv4 error messages (as opposed to ICMP informational messages or ICMP traceroute message).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="IP_Header" type="PacketObj:IPv4HeaderType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>IP header from the original datagram.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="First_Eight_Bytes" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>First 8 bytes of the original datagram's data.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv4InfoMessageType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ICMP informational messages include echo request/reply, timestamp request/reply, and address mask request/reply.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType_Echo_Reply Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType_Echo_Request Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType_Timestamp_Request Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType_Timestamp_Reply Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType_Address_Mask_Request Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType_Address_Mask_Reply Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageType_Info_Msg_Content
Used by
Children PacketObj:Address_Mask_Reply, PacketObj:Address_Mask_Request, PacketObj:Echo_Reply, PacketObj:Echo_Request, PacketObj:Info_Msg_Content, PacketObj:Timestamp_Reply, PacketObj:Timestamp_Request
Source
 
<xs:complexType name="ICMPv4InfoMessageType">
  <xs:annotation>
    <xs:documentation>ICMP informational messages include echo request/reply, timestamp request/reply, and address mask request/reply.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Echo_Reply" type="PacketObj:ICMPv4EchoReplyType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Echo reply/request messages are also known as "ping". The Info_Message_Content field contains an identifier and sequence number which together form the "quench" for echo reply and echo request. Fields specific to an echo reply message are given as elements to this echo reply field (type=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Echo_Request" type="PacketObj:ICMPv4EchoRequestType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Echo reply/request messages are also known as "ping". The Info_Message_Content field contains an identifier and sequence number which together form the "quench" for echo reply and echo request. Fields specific to an echo request message are given as elements to this echo request field (type=8).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Timestamp_Request" type="PacketObj:ICMPv4TimestampRequestType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>A timestamp request is an ICMP informational message used for time synchronization.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Timestamp_Reply" type="PacketObj:ICMPv4TimestampReplyType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>A timestamp reply is an informational ICMP message which replies to a timestamp request message.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Address_Mask_Request" type="PacketObj:ICMPv4AddressMaskRequestType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>An address mask request is an ICMP informational message (query message) normally sent by a host to a router in order to obtain an appropriate subnet mask (type=17).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Address_Mask_Reply" type="PacketObj:ICMPv4AddressMaskReplyType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>An address mask reply is an ICMP informational message, used to reply to an address mask request message with an appropriate subnet mask (type=18).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="Info_Msg_Content" type="PacketObj:ICMPv4InfoMessageContentType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Fields that are common to all ICMP informational messages are defined here. Fields that are specific to individual messages are defined separately under each message type.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv4EchoReplyType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Echo reply v4 informational message (used to ping); ICMP type=0.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4EchoReplyType_Echo_Reply Network_Packet_Object_xsd.tmp#ICMPv4EchoReplyType_Data
Used by
Children PacketObj:Data, PacketObj:Echo_Reply
Source
 
<xs:complexType name="ICMPv4EchoReplyType">
  <xs:annotation>
    <xs:documentation>Echo reply v4 informational message (used to ping); ICMP type=0.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Echo_Reply" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Echo reply is the only subtype (code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This data is optional and is used for the different kind of answers given with an ICMP Echo Reply message. Can be arbitrary length (but less than the MTU of the network).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv4EchoRequestType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Echo Request informational message (used to ping); ICMP type=8.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4EchoRequestType_Echo_Request Network_Packet_Object_xsd.tmp#ICMPv4EchoRequestType_Data
Used by
Children PacketObj:Data, PacketObj:Echo_Request
Source
 
<xs:complexType name="ICMPv4EchoRequestType">
  <xs:annotation>
    <xs:documentation>Echo Request informational message (used to ping); ICMP type=8.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Echo_Request" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Echo request is the only subtype (code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This data is optional and is used for the different kind of answers given with an ICMP Echo Request message. Can be arbitrary length (but less than the MTU of the network).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv4TimestampRequestType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Time Stamp Request informational message; ICMP type=13.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4TimestampRequestType_Timestamp Network_Packet_Object_xsd.tmp#ICMPv4TimestampRequestType_Originate_Timestamp
Used by
Children PacketObj:Originate_Timestamp, PacketObj:Timestamp
Source
 
<xs:complexType name="ICMPv4TimestampRequestType">
  <xs:annotation>
    <xs:documentation>Time Stamp Request informational message; ICMP type=13.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Timestamp" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This is the only subtype of a timestamp request message (code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="Originate_Timestamp" type="cyboxCommon:UnsignedIntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>32-bits; number of ms since midnight UT. The originate timestamp is the time the sender last touched the message before sending it. If the time is not available in milliseconds 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.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv4TimestampReplyType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Time Stamp Reply informational message; ICMP type=14.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4TimestampReplyType_Timestamp_Reply Network_Packet_Object_xsd.tmp#ICMPv4TimestampReplyType_Originate_Timestamp Network_Packet_Object_xsd.tmp#ICMPv4TimestampReplyType_Receive_Timestamp Network_Packet_Object_xsd.tmp#ICMPv4TimestampReplyType_Transmit_Timestamp
Used by
Children PacketObj:Originate_Timestamp, PacketObj:Receive_Timestamp, PacketObj:Timestamp_Reply, PacketObj:Transmit_Timestamp
Source
 
<xs:complexType name="ICMPv4TimestampReplyType">
  <xs:annotation>
    <xs:documentation>Time Stamp Reply informational message; ICMP type=14.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Timestamp_Reply" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This is the only subtype of a timestamp reply message (code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="Originate_Timestamp" type="cyboxCommon:UnsignedIntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The originate timestamp is the time the sender last touched the message before sending it. If the time is not available in milliseconds 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.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Receive_Timestamp" type="cyboxCommon:UnsignedIntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The receive timestamp is the time the echoer first touched the message on receipt. If the time is not available in milliseconds 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.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Transmit_Timestamp" type="cyboxCommon:UnsignedIntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The transmit timestamp is the time the echoer last touched the message on sending it. If the time is not available in milliseconds 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.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv4AddressMaskRequestType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Address Mask Request informational message; ICMP type=17.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4AddressMaskRequestType_Address_Mask_Request Network_Packet_Object_xsd.tmp#ICMPv4AddressMaskRequestType_Address_Mask
Used by
Children PacketObj:Address_Mask, PacketObj:Address_Mask_Request
Source
 
<xs:complexType name="ICMPv4AddressMaskRequestType">
  <xs:annotation>
    <xs:documentation>Address Mask Request informational message; ICMP type=17.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Address_Mask_Request" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This is the only possible subtype of an address mask request message (code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="Address_Mask" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The address mask can be set to 0 in an address mask request message (as opposed to an address mask reply message, in which case it should be set to the subnet mask).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv4AddressMaskReplyType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Address Mask informational message; ICMP type=18.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4AddressMaskReplyType_Address_Mask_Reply Network_Packet_Object_xsd.tmp#ICMPv4AddressMaskReplyType_Address_Mask
Used by
Children PacketObj:Address_Mask, PacketObj:Address_Mask_Reply
Source
 
<xs:complexType name="ICMPv4AddressMaskReplyType">
  <xs:annotation>
    <xs:documentation>Address Mask informational message; ICMP type=18.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Address_Mask_Reply" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This is the only possible subtype of an address mask reply message (code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="Address_Mask" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This address mask field should be set to the subnet mask.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv4InfoMessageContentType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Elements associated with ICMPv4 informational messages (as opposed to ICMP error messages or ICMP traceroute message).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageContentType_Identifier Network_Packet_Object_xsd.tmp#ICMPv4InfoMessageContentType_Sequence_Number
Used by
Children PacketObj:Identifier, PacketObj:Sequence_Number
Source
 
<xs:complexType name="ICMPv4InfoMessageContentType">
  <xs:annotation>
    <xs:documentation>Elements associated with ICMPv4 informational messages (as opposed to ICMP error messages or ICMP traceroute message).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Identifier" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>16-bit identifier. Combined with the sequence number, called the "quench" for echo reply and echo request.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Sequence_Number" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>16-bit sequence number. The identifier and sequence number can be used by the client to match the reply with the request that caused the reply.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv4TracerouteType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Elements associated with ICMPv4 traceroute message (as opposed to ICMP error messages or ICMP informational messages); corresponds to ICMP type =30. (http://www.networksorcery.com/enp/protocol/icmp/msg30.htm).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType_Outbound_Packet_Forward_Success Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType_Outbound_Packet_no_Route Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType_Identifier Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType_Outbound_Hop_Count Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType_Return_Hop_Count Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType_Output_Link_Speed Network_Packet_Object_xsd.tmp#ICMPv4TracerouteType_Output_Link_MTU
Used by
Children PacketObj:Identifier, PacketObj:Outbound_Hop_Count, PacketObj:Outbound_Packet_Forward_Success, PacketObj:Outbound_Packet_no_Route, PacketObj:Output_Link_MTU, PacketObj:Output_Link_Speed, PacketObj:Return_Hop_Count
Source
 
<xs:complexType name="ICMPv4TracerouteType">
  <xs:annotation>
    <xs:documentation>Elements associated with ICMPv4 traceroute message (as opposed to ICMP error messages or ICMP informational messages); corresponds to ICMP type =30. (http://www.networksorcery.com/enp/protocol/icmp/msg30.htm).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Outbound_Packet_Forward_Success" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>One of two possible subtypes for an ICMP traceroute message. This subtype means that the outbound packet was successfully forwarded (code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Outbound_Packet_no_Route" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>One of two possible subtypes for an ICMP traceroute message. This one means that there is no route for the outbound packet and the packet was discarded (code=1).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="Identifier" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>16 bits. The ID number as copied from the ICMP traceroute option of the packet which caused this traceroute message to be sent (not related to the ID number in the IP header). (http://www.networksorcery.com/enp/protocol/icmp/msg30.htm).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Outbound_Hop_Count" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>16 bits. Outbound hop count as copied from the IP traceroute option of the packet which caused this traceroute message to be sent (http://www.networksorcery.com/enp/protocol/icmp/msg30.htm).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Return_Hop_Count" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>16 bits. Return hop count as copied from the IP traceroute options of the packet which caused this traceroute message to be sent. (http://www.networksorcery.com/enp/protocol/icmp/msg30.htm).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Output_Link_Speed" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>32 bits. The speed in bytes per second of the link over which the Outbound/Return Packet will be sent. If this value cannot be determined, the field should be set to zero. (http://www.networksorcery.com/enp/protocol/icmp/msg30.htm).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Output_Link_MTU" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>32 bits. The MTU in bytes of the link over which the Outbound/Return Packet will be sent. MTU refers to the data portion (includes IP header; excludes datalink header/trailer) of the packet. If this value cannot be determined, this field should be set to zero. (http://www.networksorcery.com/enp/protocol/icmp/msg30.htm).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:IPv6PacketType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Internet Protocol version 6 (IPv6) is intended to succeed IPv4, and like IPv4 it is a connectionless protocol for use on packet-switched link layer networks. RFC 3513, RFC 2460, http://en.wikipedia.org/wiki/IPv6.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv6PacketType_IPv6_Header Network_Packet_Object_xsd.tmp#IPv6PacketType_Ext_Headers Network_Packet_Object_xsd.tmp#IPv6PacketType_Data
Used by
Children PacketObj:Data, PacketObj:Ext_Headers, PacketObj:IPv6_Header
Source
 
<xs:complexType name="IPv6PacketType">
  <xs:annotation>
    <xs:documentation>Internet Protocol version 6 (IPv6) is intended to succeed IPv4, and like IPv4 it is a connectionless protocol for use on packet-switched link layer networks. RFC 3513, RFC 2460, http://en.wikipedia.org/wiki/IPv6.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="IPv6_Header" type="PacketObj:IPv6HeaderType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>IPv6 headers is a simplification of the IPv4 header.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Ext_Headers" type="PacketObj:IPv6ExtHeaderType" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>In IPv6, optional internet-layer information is encoded in separate headers that may be placed between the IPv6 header and the upper-layer header in a packet. http://tools.ietf.org/html/rfc2460.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The data portion of an IP packet. Actual field values will probably be specified in the elements of the different network layers, but we provide a field here to capture any data as necessary.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:IPv6HeaderType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The IPv6 header is a simplification of the IPv4 header.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv6HeaderType_IP_Version Network_Packet_Object_xsd.tmp#IPv6HeaderType_Traffic_Class Network_Packet_Object_xsd.tmp#IPv6HeaderType_Flow_Label Network_Packet_Object_xsd.tmp#IPv6HeaderType_Payload_Length Network_Packet_Object_xsd.tmp#IPv6HeaderType_Next_Header Network_Packet_Object_xsd.tmp#IPv6HeaderType_TTL Network_Packet_Object_xsd.tmp#IPv6HeaderType_Src_IPv6_Addr Network_Packet_Object_xsd.tmp#IPv6HeaderType_Dest_IPv6_Addr
Used by
Children PacketObj:Dest_IPv6_Addr, PacketObj:Flow_Label, PacketObj:IP_Version, PacketObj:Next_Header, PacketObj:Payload_Length, PacketObj:Src_IPv6_Addr, PacketObj:TTL, PacketObj:Traffic_Class
Source
 
<xs:complexType name="IPv6HeaderType">
  <xs:annotation>
    <xs:documentation>The IPv6 header is a simplification of the IPv4 header.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="IP_Version" type="PacketObj:IPVersionType" fixed="IPv6(6)" minOccurs="0">
      <xs:annotation>
        <xs:documentation>4-bit Internet Protocol version number =6.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Traffic_Class" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>8-bit traffic class field. Available for use by originating nodes and/or forwarding routers to identify and distinguish between different classes or priorities of IPv6 packets. http://tools.ietf.org/html/rfc2460#section-7.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Flow_Label" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>20-bit flow label. Used by a source to label sequences of packets for which it requests special handling by the IPv6 routers, such as non-default quality of service. http://tools.ietf.org/html/rfc2460#section-6.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Payload_Length" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>16-bit unsigned integer. Length of the IPv6 payload (the rest of the packet following the IPv6 header) in octets. Any extension headers are considered part of the payload.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Next_Header" type="PacketObj:IANAAssignedIPNumbersType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>8-bit selector. Identifies the type of header immediately following the IPv6 header. Uses the same values as the IPv4 protocol field.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="TTL" type="cyboxCommon:PositiveIntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>TTL/hop limit specifies how many times a packet can be forwarded. 8-bit unsigned integer.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Src_IPv6_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>128-bit address of the originator of the packet.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Dest_IPv6_Addr" type="AddressObj:AddressObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>128-bit address of the intended recipient of the packet.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:IPv6ExtHeaderType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
In IPv6, optional internet-layer information is encoded in separate headers that may be placed between the IPv6 header and the upper-layer header in a packet. An IPv6 packet may carry zero, one, or more extension headers, each identified by the Next Header field of the preceding header. http://tools.ietf.org/html/rfc2460.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv6ExtHeaderType_Hop_by_Hop_Options Network_Packet_Object_xsd.tmp#IPv6ExtHeaderType_Routing Network_Packet_Object_xsd.tmp#IPv6ExtHeaderType_Fragment Network_Packet_Object_xsd.tmp#IPv6ExtHeaderType_Destination_Options Network_Packet_Object_xsd.tmp#IPv6ExtHeaderType_Authentication_Header Network_Packet_Object_xsd.tmp#IPv6ExtHeaderType_Encapsulating_Security_Payload
Used by
Children PacketObj:Authentication_Header, PacketObj:Destination_Options, PacketObj:Encapsulating_Security_Payload, PacketObj:Fragment, PacketObj:Hop_by_Hop_Options, PacketObj:Routing
Source
 
<xs:complexType name="IPv6ExtHeaderType">
  <xs:annotation>
    <xs:documentation>In IPv6, optional internet-layer information is encoded in separate headers that may be placed between the IPv6 header and the upper-layer header in a packet. An IPv6 packet may carry zero, one, or more extension headers, each identified by the Next Header field of the preceding header. http://tools.ietf.org/html/rfc2460.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="Hop_by_Hop_Options" type="PacketObj:HopByHopOptionsType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The Hop-by-Hop Options header is used to carry optional information that must be examined by every node along a packet's delivery path. It carries a variable number of type-length-value (TLV) encoded options.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Routing" type="PacketObj:RoutingType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The Routing header is used by an IPv6 source to list one or more intermediate nodes to be "visited" on the way to a packet's destination. http://tools.ietf.org/html/rfc2460.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Fragment" type="PacketObj:FragmentType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The Fragment header is used by an IPv6 source to send a packet larger than would fit in the path MTU. A fragment packet begins with an unfragmentable part consisting of the IPv6 header plus all extension headers up to and including the routing header. We don't include it for this field because the data is already stored in other elements. We provide the elements necessary for the Fragmentable Part. http://tools.ietf.org/html/rfc2460.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Destination_Options" type="PacketObj:DestinationOptionsType" minOccurs="0" maxOccurs="2">
      <xs:annotation>
        <xs:documentation>The Destination Options header is used to carry optional information that needs to be examined only by a packet's destination node(s).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Authentication_Header" type="PacketObj:AuthenticationHeaderType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Follows RFC2402. The IP Authentication Header is used to provide connectionless integrity and data origin authentication for IP datagrams and to provide protection against replays. http://www.ietf.org/rfc/rfc2402.txt.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Encapsulating_Security_Payload" type="PacketObj:EncapsulatingSecurityPayloadType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Follows RFC2406. ESP is used to provide confidentiality, data origin authentication, connectionless integrity, an anti-replay service (a form of partial sequence integrity), and limited traffic flow confidentiality.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:HopByHopOptionsType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Defines fields for the IPv6 Hop-by-Hop Options header which is used to carry optional information that must be examined by every node along a packet's delivery path.
Diagram
Diagram Network_Packet_Object_xsd.tmp#HopByHopOptionsType_Next_Header Network_Packet_Object_xsd.tmp#HopByHopOptionsType_Header_Ext_Len Network_Packet_Object_xsd.tmp#HopByHopOptionsType_Option_Data
Used by
Children PacketObj:Header_Ext_Len, PacketObj:Next_Header, PacketObj:Option_Data
Source
 
<xs:complexType name="HopByHopOptionsType">
  <xs:annotation>
    <xs:documentation>Defines fields for the IPv6 Hop-by-Hop Options header which is used to carry optional information that must be examined by every node along a packet's delivery path.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Next_Header" type="PacketObj:IANAAssignedIPNumbersType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Identifies the type of header immediately following the Hop-by-Hop Options header. Uses the same values as the IPv4 Protocol field.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Header_Ext_Len" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Length of the Hop-by-Hop Options header in 8-octet units, not including the first 8 octets.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Option_Data" type="PacketObj:OptionDataType" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Variable-length field, of length such that the complete Hop-by-Hop Options header is an integer multiple of 8 octets long. Contains one or more type-length-value (TLV)-encoded options.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:OptionDataType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Defines the variable-length fields associated with IPv6 extension headers (the Hop-by-Hop Options header and the Destination Options header). Contains one or more type-length-value (TLV)-encoded options.
Diagram
Diagram Network_Packet_Object_xsd.tmp#OptionDataType_Option_Type Network_Packet_Object_xsd.tmp#OptionDataType_Option_Data_Len Network_Packet_Object_xsd.tmp#OptionDataType_Pad1 Network_Packet_Object_xsd.tmp#OptionDataType_PadN
Used by
Children PacketObj:Option_Data_Len, PacketObj:Option_Type, PacketObj:Pad1, PacketObj:PadN
Source
 
<xs:complexType name="OptionDataType">
  <xs:annotation>
    <xs:documentation>Defines the variable-length fields associated with IPv6 extension headers (the Hop-by-Hop Options header and the Destination Options header). Contains one or more type-length-value (TLV)-encoded options.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Option_Type" type="PacketObj:IPv6OptionType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Identifies the type of option. This 8-bit Option Type identifier is internally encoded such that different bits have different meanings. These meanings are further specified in the IPv6OptionType type.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Option_Data_Len" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Length of the Option Data field of this option, in octets.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:choice minOccurs="0">
      <xs:annotation>
        <xs:documentation/>
      </xs:annotation>
      <xs:element name="Pad1" type="PacketObj:Pad1Type" minOccurs="0">
        <xs:annotation>
          <xs:documentation>The Pad1 option is used to insert one octet of padding into the Options area of a header. The Pad1 option does not have length and value fields.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="PadN" type="PacketObj:PadNType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>The PadN option is used to insert two or more octets of paddings into the Options area of a header.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:IPv6OptionType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Specifies the meaning of each bit of the 8-bit IPv6OptionType type.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv6OptionType_Do_Not_Recogn_Action Network_Packet_Object_xsd.tmp#IPv6OptionType_Packet_Change Network_Packet_Object_xsd.tmp#IPv6OptionType_Option_Byte
Used by
Children PacketObj:Do_Not_Recogn_Action, PacketObj:Option_Byte, PacketObj:Packet_Change
Source
 
<xs:complexType name="IPv6OptionType">
  <xs:annotation>
    <xs:documentation>Specifies the meaning of each bit of the 8-bit IPv6OptionType type.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Do_Not_Recogn_Action" type="PacketObj:IPv6DoNotRecogActionType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Action to be taken if the processing IPv6 nodes does not recognize the Option Type. This information is internally encoded in the Option Type identifier (highest-order two bits) such that their highest-order two bits specify the action that must be taken if the processing IPv6 node does not recognize the Option type. These possible actions are enumerated via IPv6DoNotRecogActionType.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Packet_Change" type="PacketObj:IPv6PacketChangeType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The third highest order bit of the Option Data specifies whether or not the Option Data of that option can change en-route to the packet's final destination.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Option_Byte" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field may be used to specify the actual Option Type byte, with no explicit meaning attached. Meaning/interpretation provided by the Do_Not_Recogn_Action and Packet_Change fields.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:IPv6DoNotRecogActionType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
IPv6DoNotRecogActionType specifies possible actions when option is not recognized, via a union of the IPv6DoNotRecogActionTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv6DoNotRecogActionType_datatype
Type restriction of BaseObjectPropertyType
Type hierarchy
Used by
Source
 
<xs:complexType name="IPv6DoNotRecogActionType">
  <xs:annotation>
    <xs:documentation>IPv6DoNotRecogActionType specifies possible actions when option is not recognized, via a union of the IPv6DoNotRecogActionTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:restriction base="cyboxCommon:BaseObjectPropertyType">
      <xs:simpleType>
        <xs:union memberTypes="PacketObj:IPv6DoNotRecogActionTypeEnum xs:string"/>
      </xs:simpleType>
      <xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
        <xs:annotation>
          <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
  </xs:simpleContent>
</xs:complexType>
Complex Type PacketObj:IPv6PacketChangeType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
IPV6PacketChangeType specifies whether a packet has changed, via a union of the IPv6PacketChangeTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IPv6PacketChangeType_datatype
Type restriction of BaseObjectPropertyType
Type hierarchy
Used by
Source
 
<xs:complexType name="IPv6PacketChangeType">
  <xs:annotation>
    <xs:documentation>IPV6PacketChangeType specifies whether a packet has changed, via a union of the IPv6PacketChangeTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:restriction base="cyboxCommon:BaseObjectPropertyType">
      <xs:simpleType>
        <xs:union memberTypes="PacketObj:IPv6PacketChangeTypeEnum xs:string"/>
      </xs:simpleType>
      <xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
        <xs:annotation>
          <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
  </xs:simpleContent>
</xs:complexType>
Complex Type PacketObj:Pad1Type
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Pad1 type specifies how one octet of padding is inserted into the Options area of a header. The Pad1 option type does not have length and value fields.
Diagram
Diagram Network_Packet_Object_xsd.tmp#Pad1Type_Octet
Used by
Children PacketObj:Octet
Source
 
<xs:complexType name="Pad1Type">
  <xs:annotation>
    <xs:documentation>The Pad1 type specifies how one octet of padding is inserted into the Options area of a header. The Pad1 option type does not have length and value fields.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Octet" type="cyboxCommon:HexBinaryObjectPropertyType" fixed="00">
      <xs:annotation>
        <xs:documentation>The fixed 00 value specifies that the Pad1 option is used and also serves as the single octet of padding.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:PadNType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The PadN type specifies how two or more octets of padding are inserted into the Options area of a header.
Diagram
Diagram Network_Packet_Object_xsd.tmp#PadNType_Octet Network_Packet_Object_xsd.tmp#PadNType_Option_Data_Length Network_Packet_Object_xsd.tmp#PadNType_Option_Data
Used by
Children PacketObj:Octet, PacketObj:Option_Data, PacketObj:Option_Data_Length
Source
 
<xs:complexType name="PadNType">
  <xs:annotation>
    <xs:documentation>The PadN type specifies how two or more octets of padding are inserted into the Options area of a header.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Octet" type="cyboxCommon:HexBinaryObjectPropertyType" fixed="01" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Specifies the PandN option.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Option_Data_Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Length of the padding. For N octets of padding, the Option_Data_Length fields contains the value N-2.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Option_Data" type="cyboxCommon:IntegerObjectPropertyType" fixed="00" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Actual padding; consists of N-2 zero-valued octets.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:RoutingType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Specifies the fields of the Routing header, which is used by an IPv6 source to list one or more intermediate nodes to be "visited" on the way to a packet's destination. http://tools.ietf.org/html/rfc2460.
Diagram
Diagram Network_Packet_Object_xsd.tmp#RoutingType_Next_Header Network_Packet_Object_xsd.tmp#RoutingType_Header_Ext_Len Network_Packet_Object_xsd.tmp#RoutingType_Routing_Type Network_Packet_Object_xsd.tmp#RoutingType_Segments_Left Network_Packet_Object_xsd.tmp#RoutingType_Type_Specific_Data
Used by
Children PacketObj:Header_Ext_Len, PacketObj:Next_Header, PacketObj:Routing_Type, PacketObj:Segments_Left, PacketObj:Type_Specific_Data
Source
 
<xs:complexType name="RoutingType">
  <xs:annotation>
    <xs:documentation>Specifies the fields of the Routing header, which is used by an IPv6 source to list one or more intermediate nodes to be "visited" on the way to a packet's destination. http://tools.ietf.org/html/rfc2460.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Next_Header" type="PacketObj:IANAAssignedIPNumbersType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Identifies the type of header immediately following the Routing header. Uses the same values as the IPv4 Protocol field.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Header_Ext_Len" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>length of the Routing header in 8-octet units, not including the first 8 octets.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Routing_Type" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>8-bit identifiers of a particular Routing header variant. Further definition will be added as required.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Segments_Left" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Number of route segments remaining, i.e., number of explicitly listed intermediate nodes still to be visited before reaching the final destination. http://tools.ietf.org/html/rfc2460.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Type_Specific_Data" type="cyboxCommon:StringObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Variable length field, of format determined by the Routing Type.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:FragmentType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Specifies the fields of the Fragment header, which is used by an IPv6 source to send a packet larger than would fit in the path MTU. http://tools.ietf.org/html/rfc2460.
Diagram
Diagram Network_Packet_Object_xsd.tmp#FragmentType_Fragment_Header Network_Packet_Object_xsd.tmp#FragmentType_Fragment
Used by
Children PacketObj:Fragment, PacketObj:Fragment_Header
Source
 
<xs:complexType name="FragmentType">
  <xs:annotation>
    <xs:documentation>Specifies the fields of the Fragment header, which is used by an IPv6 source to send a packet larger than would fit in the path MTU. http://tools.ietf.org/html/rfc2460.</xs:documentation>
  </xs:annotation>
  <xs:sequence minOccurs="0" maxOccurs="unbounded">
    <xs:element name="Fragment_Header" type="PacketObj:FragmentHeaderType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Each fragment has a header containing next header information, the offset of the fragment, an M flag specifying whether or not it is the last fragment, and an identification value.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Fragment" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The fragment of the packet that corresponds to the fragment header. The length of the fragment must fit with the MTU of the path to the packets' destination.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:FragmentHeaderType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Each fragment has a header containing next header information, the offset of the fragment, an M flag specifying whether or not it is the last fragment, and an identification value.
Diagram
Diagram Network_Packet_Object_xsd.tmp#FragmentHeaderType_Next_Header Network_Packet_Object_xsd.tmp#FragmentHeaderType_Fragment_Offset Network_Packet_Object_xsd.tmp#FragmentHeaderType_M_Flag Network_Packet_Object_xsd.tmp#FragmentHeaderType_Identification
Used by
Children PacketObj:Fragment_Offset, PacketObj:Identification, PacketObj:M_Flag, PacketObj:Next_Header
Source
 
<xs:complexType name="FragmentHeaderType">
  <xs:annotation>
    <xs:documentation>Each fragment has a header containing next header information, the offset of the fragment, an M flag specifying whether or not it is the last fragment, and an identification value.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Next_Header" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Identifies the type of header immediately following the Fragment header. Uses the same values as the IPv4 Protocol field.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Fragment_Offset" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>13-bit unsigned integer. The offset, in 8-octet units, of the data following this header, relative to the start of the Fragmentable Part or the original packet.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="M_Flag" type="PacketObj:MFlagType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Indicates whether this is the last fragment or whether there are more fragments.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Identification" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>For every packet that is to be fragmented, the source node generates a 32-bit Identification value.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:MFlagType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
MFlagType specifies whether there are more fragments, via a union of the MFlagTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.
Diagram
Diagram Network_Packet_Object_xsd.tmp#MFlagType_datatype
Type restriction of BaseObjectPropertyType
Type hierarchy
Used by
Source
 
<xs:complexType name="MFlagType">
  <xs:annotation>
    <xs:documentation>MFlagType specifies whether there are more fragments, via a union of the MFlagTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:restriction base="cyboxCommon:BaseObjectPropertyType">
      <xs:simpleType>
        <xs:union memberTypes="PacketObj:MFlagTypeEnum xs:string"/>
      </xs:simpleType>
      <xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
        <xs:annotation>
          <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
  </xs:simpleContent>
</xs:complexType>
Complex Type PacketObj:DestinationOptionsType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Defines fields for the IPv6 Destination Options header which is used to carry optional information that needs to be examined only by a packet's destination node(s).
Diagram
Diagram Network_Packet_Object_xsd.tmp#DestinationOptionsType_Next_Header Network_Packet_Object_xsd.tmp#DestinationOptionsType_Header_Ext_Len Network_Packet_Object_xsd.tmp#DestinationOptionsType_Option_Data
Used by
Children PacketObj:Header_Ext_Len, PacketObj:Next_Header, PacketObj:Option_Data
Source
 
<xs:complexType name="DestinationOptionsType">
  <xs:annotation>
    <xs:documentation>Defines fields for the IPv6 Destination Options header which is used to carry optional information that needs to be examined only by a packet's destination node(s).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Next_Header" type="PacketObj:IANAAssignedIPNumbersType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Identifies the type of header immediately following the Destination_Options options header. Uses the same values as the IPv4 Protocol field.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Header_Ext_Len" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Length of the Destination Options header in 8-octet units, not including the first 8 octets.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Option_Data" type="PacketObj:OptionDataType" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Variable-length field, of length such that the complete Destinations Options header is an integer multiple of 8 octets long. Contains one or more type-length-value (TLV)-encoded options.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:AuthenticationHeaderType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The IP Authentication Header is used to provide connectionless integrity and data origin authentication for IP datagrams and to provide protection against replays. http://www.ietf.org/rfc/rfc2402.txt.
Diagram
Diagram Network_Packet_Object_xsd.tmp#AuthenticationHeaderType_Next_Header Network_Packet_Object_xsd.tmp#AuthenticationHeaderType_Header_Ext_Len Network_Packet_Object_xsd.tmp#AuthenticationHeaderType_Security_Parameters_Index Network_Packet_Object_xsd.tmp#AuthenticationHeaderType_Sequence_Number Network_Packet_Object_xsd.tmp#AuthenticationHeaderType_Authentication_Data
Used by
Children PacketObj:Authentication_Data, PacketObj:Header_Ext_Len, PacketObj:Next_Header, PacketObj:Security_Parameters_Index, PacketObj:Sequence_Number
Source
 
<xs:complexType name="AuthenticationHeaderType">
  <xs:annotation>
    <xs:documentation>The IP Authentication Header is used to provide connectionless integrity and data origin authentication for IP datagrams and to provide protection against replays. http://www.ietf.org/rfc/rfc2402.txt.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Next_Header" type="PacketObj:IANAAssignedIPNumbersType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Identifies the type of header immediately following the Authentication header. Uses the same values as the IPv4 Protocol field.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Header_Ext_Len" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>An 8-bit field specifying the length of the AH in 32-bit words.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Security_Parameters_Index" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The SPI is an arbitrary 32-bit value that, in combination with the destination IP address and security protocol (AH), uniquely identifies the Security Association for this datagram. The set of SPI values in the range 1 through 255 are reserved by the Internet Assigned Numbers Authority (IANA) for future use. http://www.ietf.org/rfc/rfc2402.txt.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Sequence_Number" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This unsigned 32-bit field contains a monotonically increasing counter value (sequence number).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Authentication_Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This is a variable-length field that contains the Integrity Check Value (ICV) for this packet. The field must be an integer multiple of 32 bits in length.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:EncapsulatingSecurityPayloadType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ESP is used to provide confidentiality, data origin authentication, connectionless integrity, an anti-replay service (a form of partial sequence integrity), and limited traffic flow confidentiality. http://www.ietf.org/rfc/rfc2406.txt.
Diagram
Diagram Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType_Security_Parameters_Index Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType_Sequence_Number Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType_Payload_Data Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType_Padding Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType_Padding_Len Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType_Next_Header Network_Packet_Object_xsd.tmp#EncapsulatingSecurityPayloadType_Authentication_Data
Used by
Children PacketObj:Authentication_Data, PacketObj:Next_Header, PacketObj:Padding, PacketObj:Padding_Len, PacketObj:Payload_Data, PacketObj:Security_Parameters_Index, PacketObj:Sequence_Number
Source
 
<xs:complexType name="EncapsulatingSecurityPayloadType">
  <xs:annotation>
    <xs:documentation>ESP is used to provide confidentiality, data origin authentication, connectionless integrity, an anti-replay service (a form of partial sequence integrity), and limited traffic flow confidentiality. http://www.ietf.org/rfc/rfc2406.txt.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Security_Parameters_Index" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The SPI is an arbitrary 32-bit value that, in combination with the destination IP address and security protocol (ESP), uniquely identifies the Security Association for this datagram. http://www.ietf.org/rfc/rfc2406.txt.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Sequence_Number" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This unsigned 32-bit field contains a monotonically increasing counter value (sequence number).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Payload_Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Payload Data is a variable-length field containing data described by the Next Header field.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Padding" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The padding field can be used for various reasons, such as to fill in the plaintext as required by an encryption algorithm or to conceal the actual length of the payload.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Padding_Len" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The pad length indicates the number of pad bytes immediately preceding it. Range is 0-255, where a value of zero indicates that no padding bytes are present. http://www.ietf.org/rfc/rfc2406.txt.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Next_Header" type="PacketObj:IANAAssignedIPNumbersType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Identifies the type data contained in the payload data field. Uses the same values as the IPv4 Protocol field.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Authentication_Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The Authentication Data is a variable-length field containing an Integrity Check Value (ICV) computed over the ESP packet minus the Authentication Data. http://www.ietf.org/rfc/rfc2406.txt.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv6PacketType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ICMP is used to send error messages (e.g., a datagram cannot reach its destination), informational messages ( e.g., ping). Only the message types defined in RFC 4443 (ICMP v6) are included; additional message types will be defined as needed. REF: http://tools.ietf.org/html/rfc4443 and http://www.networksorcery.com/enp/protocol/icmpv6.htm and http://en.wikipedia.org/wiki/ICMPv6.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6PacketType_ICMPv6_Header Network_Packet_Object_xsd.tmp#ICMPv6PacketType_Error_Msg Network_Packet_Object_xsd.tmp#ICMPv6PacketType_Info_Msg
Used by
Children PacketObj:Error_Msg, PacketObj:ICMPv6_Header, PacketObj:Info_Msg
Source
 
<xs:complexType name="ICMPv6PacketType">
  <xs:annotation>
    <xs:documentation>ICMP is used to send error messages (e.g., a datagram cannot reach its destination), informational messages ( e.g., ping). Only the message types defined in RFC 4443 (ICMP v6) are included; additional message types will be defined as needed. REF: http://tools.ietf.org/html/rfc4443 and http://www.networksorcery.com/enp/protocol/icmpv6.htm and http://en.wikipedia.org/wiki/ICMPv6.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="ICMPv6_Header" type="PacketObj:ICMPv6HeaderType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Actual ICMP v6 header bytes are defined, corresponding to the ICMP type, ICMP code, and to the checksum.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:choice minOccurs="0">
      <xs:element name="Error_Msg" type="PacketObj:ICMPv6ErrorMessageType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>For ICMP v6 error messages, boolean values are used in this field to explicitly interpret the type and code bytes appearing in the ICMP header. Additional fields and message content are also defined here. The type value indicates whether an ICMP message is an error message (type is 0 to 127) or an information message (type is 128 to 255).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Info_Msg" type="PacketObj:ICMPv6InfoMessageType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>For ICMP v6 informational messages, boolean values are used in this field to explicitly interpret the type and code bytes appearing in the ICMP header. Additional fields and message content are also defined here. The type value indicates whether an ICMP message is an error message (type is 0 to 127) or an information message (type is 128 to 255).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv6ErrorMessageType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ICMP v6 error messages include destination unreachable messages, packet too big messages, and time exceeded messages, and parameter problem messages, as defined in RFC 2463. Type values of ICMP v6 error messages range from 1 to 127.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6ErrorMessageType_Destination_Unreachable Network_Packet_Object_xsd.tmp#ICMPv6ErrorMessageType_Packet_Too_Big Network_Packet_Object_xsd.tmp#ICMPv6ErrorMessageType_Time_Exceeded Network_Packet_Object_xsd.tmp#ICMPv6ErrorMessageType_Parameter_Problem Network_Packet_Object_xsd.tmp#ICMPv6ErrorMessageType_Invoking_Packet
Used by
Children PacketObj:Destination_Unreachable, PacketObj:Invoking_Packet, PacketObj:Packet_Too_Big, PacketObj:Parameter_Problem, PacketObj:Time_Exceeded
Source
 
<xs:complexType name="ICMPv6ErrorMessageType">
  <xs:annotation>
    <xs:documentation>ICMP v6 error messages include destination unreachable messages, packet too big messages, and time exceeded messages, and parameter problem messages, as defined in RFC 2463. Type values of ICMP v6 error messages range from 1 to 127.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Destination_Unreachable" type="PacketObj:ICMPv6DestinationUnreachableType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>A destination unreachable message should be generated by a router, or by the IPv6 later in the originating node, in response to a packet that cannot be delivered to its destination address for reasons other than congestion. (http://tools.ietf.org/html/rfc4443).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Packet_Too_Big" type="PacketObj:ICMPv6PacketTooBigType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>A packet too big message must be sent by a router in response to a packet that it cannot forward because the packet is larger than the MTU of the outgoing link.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Time_Exceeded" type="PacketObj:ICMPv6TimeExceededType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>A time exceeded message is send if either the hop limit is exceeded (hop limit = 0) or if fragment reassembly has timed out.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Parameter_Problem" type="PacketObj:ICMPv6ParameterProblemType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>If an IPv6 node processing a packet finds a problem with a field in the IPv6 header or extension headers and it cannot complete processing of the packet, it should send an ICMPv6 Parameter Problem message to the packet's source (http://tools.ietf.org/html/rfc4443).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="Invoking_Packet" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPc6 MTU.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv6DestinationUnreachableType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Destination unreachable error message; ICMP v6 type=1.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType_No_Route Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType_Comm_Prohibited Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType_Beyond_Scope Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType_Address_Unreachable Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType_Port_Unreachable Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType_Src_Addr_Failed_Policy Network_Packet_Object_xsd.tmp#ICMPv6DestinationUnreachableType_Reject_Route
Used by
Children PacketObj:Address_Unreachable, PacketObj:Beyond_Scope, PacketObj:Comm_Prohibited, PacketObj:No_Route, PacketObj:Port_Unreachable, PacketObj:Reject_Route, PacketObj:Src_Addr_Failed_Policy
Source
 
<xs:complexType name="ICMPv6DestinationUnreachableType">
  <xs:annotation>
    <xs:documentation>Destination unreachable error message; ICMP v6 type=1.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="No_Route" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>No route to destination (ICMP v6 code=0).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Comm_Prohibited" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Communication with destination administratively prohibited (ICMP v6 code=1).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Beyond_Scope" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Beyond scope of source address (ICMP v6 code =2).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Address_Unreachable" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Address is unreachable (ICMP v6 code=3).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Port_Unreachable" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Port is unreachable (ICMP v6 code=4).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Src_Addr_Failed_Policy" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Source address failed ingress/egress policy (ICMP v6 code=5).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Reject_Route" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Reject route to destination (ICMP v6 code=6).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:ICMPv6PacketTooBigType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Packet too big error message; ICMP v6 type=2.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6PacketTooBigType_Packet_Too_Big Network_Packet_Object_xsd.tmp#ICMPv6PacketTooBigType_MTU
Used by
Children PacketObj:MTU, PacketObj:Packet_Too_Big
Source
 
<xs:complexType name="ICMPv6PacketTooBigType">
  <xs:annotation>
    <xs:documentation>Packet too big error message; ICMP v6 type=2.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Packet_Too_Big" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Only one code value is defined and is set to 0 (zero) by the originator and ignored by the receiver.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="MTU" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Maximum Transmission Unit describes the size limit for any given physical network.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv6TimeExceededType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Time exceeded error message; ICMP v6 type=3.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6TimeExceededType_Hop_Limit_Exceeded Network_Packet_Object_xsd.tmp#ICMPv6TimeExceededType_Fragment_Reassem_Time_Exceeded
Used by
Children PacketObj:Fragment_Reassem_Time_Exceeded, PacketObj:Hop_Limit_Exceeded
Source
 
<xs:complexType name="ICMPv6TimeExceededType">
  <xs:annotation>
    <xs:documentation>Time exceeded error message; ICMP v6 type=3.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="Hop_Limit_Exceeded" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Hop limit exceeded in transit (ICMP v6 code=0).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Fragment_Reassem_Time_Exceeded" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Fragment reassembly time exceeded (ICMP v6 code=1).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:ICMPv6ParameterProblemType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Parameter problem error message; ICMP v6 type=4.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6ParameterProblemType_Erroneous_Header_Field Network_Packet_Object_xsd.tmp#ICMPv6ParameterProblemType_Unrecognized_Next_Header_Type Network_Packet_Object_xsd.tmp#ICMPv6ParameterProblemType_Unrecognized_IPv6_Option Network_Packet_Object_xsd.tmp#ICMPv6ParameterProblemType_Pointer
Used by
Children PacketObj:Erroneous_Header_Field, PacketObj:Pointer, PacketObj:Unrecognized_IPv6_Option, PacketObj:Unrecognized_Next_Header_Type
Source
 
<xs:complexType name="ICMPv6ParameterProblemType">
  <xs:annotation>
    <xs:documentation>Parameter problem error message; ICMP v6 type=4.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Erroneous_Header_Field" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Erroneous header field encountered (ICMP v6 code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Unrecognized_Next_Header_Type" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Unrecognized next header type encountered (ICMP v6 code=1).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Unrecognized_IPv6_Option" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Unrecognized IP v6 option encountered (ICMP v6 code=2).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="Pointer" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>identifies octet offset within invoking packet where error was detected.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv6InfoMessageType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ICMP v6 informational messages include echo request/reply; other informational message types will be added in the future as they are more commonly used (only echo request/reply are defined in RFC 4443).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6InfoMessageType_Echo_Request Network_Packet_Object_xsd.tmp#ICMPv6InfoMessageType_Echo_Reply Network_Packet_Object_xsd.tmp#ICMPv6InfoMessageType_Info_Msg_Content
Used by
Children PacketObj:Echo_Reply, PacketObj:Echo_Request, PacketObj:Info_Msg_Content
Source
 
<xs:complexType name="ICMPv6InfoMessageType">
  <xs:annotation>
    <xs:documentation>ICMP v6 informational messages include echo request/reply; other informational message types will be added in the future as they are more commonly used (only echo request/reply are defined in RFC 4443).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Echo_Request" type="PacketObj:ICMPv6EchoRequestType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Echo request and reply messages are used for diagnostic purposes.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Echo_Reply" type="PacketObj:ICMPv6EchoReplyType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Echo request and reply messages are used for diagnostic purposes.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="Info_Msg_Content" type="PacketObj:ICMPv6InfoMessageContentType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Fields that are common to all ICMP v6 informational messages are defined here. Fields that are specific to individual messages are defined separately under each message type.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv6EchoRequestType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Echo request informational ICMP v6 message; type=128.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6EchoRequestType_Echo_Request Network_Packet_Object_xsd.tmp#ICMPv6EchoRequestType_Data
Used by
Children PacketObj:Data, PacketObj:Echo_Request
Source
 
<xs:complexType name="ICMPv6EchoRequestType">
  <xs:annotation>
    <xs:documentation>Echo request informational ICMP v6 message; type=128.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice minOccurs="0">
      <xs:element name="Echo_Request" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Every node must implement an ICMP v6 Echo responder function that receives Echo Requests (ICMP v6 code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Zero or more octets of arbitrary data.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:ICMPv6EchoReplyType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Echo reply informational ICMP v6 message; type=129.
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6EchoReplyType_Echo_Reply Network_Packet_Object_xsd.tmp#ICMPv6EchoReplyType_Data
Used by
Children PacketObj:Data, PacketObj:Echo_Reply
Source
 
<xs:complexType name="ICMPv6EchoReplyType">
  <xs:annotation>
    <xs:documentation>Echo reply informational ICMP v6 message; type=129.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:choice minOccurs="0">
      <xs:element name="Echo_Reply" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Every node must implement an ICMP v6 Echo responder function that originates corresponding Echo Replies(ICMP v6 code=0).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="Data" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This is the data from the invoking echo request message.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:ICMPv6InfoMessageContentType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Elements associated with ICMPv6 informational messages (as opposed to ICMP v6 error messages).
Diagram
Diagram Network_Packet_Object_xsd.tmp#ICMPv6InfoMessageContentType_Identifier Network_Packet_Object_xsd.tmp#ICMPv6InfoMessageContentType_Sequence_Number
Used by
Children PacketObj:Identifier, PacketObj:Sequence_Number
Source
 
<xs:complexType name="ICMPv6InfoMessageContentType">
  <xs:annotation>
    <xs:documentation>Elements associated with ICMPv6 informational messages (as opposed to ICMP v6 error messages).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Identifier" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>16-bit identifier. Combined with the sequence number, called the "quench" for echo reply and echo request.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Sequence_Number" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>16-bit sequence number. The identifier and sequence number can be used by the client to match the reply with the request that caused the reply.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:TransportLayerType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
only UDP and TCP defined to begin. Other protocols will be defined as necessary.
Diagram
Diagram Network_Packet_Object_xsd.tmp#TransportLayerType_TCP Network_Packet_Object_xsd.tmp#TransportLayerType_UDP
Used by
Children PacketObj:TCP, PacketObj:UDP
Source
 
<xs:complexType name="TransportLayerType">
  <xs:annotation>
    <xs:documentation>only UDP and TCP defined to begin. Other protocols will be defined as necessary.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:annotation>
      <xs:documentation/>
    </xs:annotation>
    <xs:element name="TCP" type="PacketObj:TCPType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>TCP provides reliable, ordered delivery of a stream of bytes from a program on one computer to another program on another computer. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="UDP" type="PacketObj:UDPType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>UDP uses a simple transmission model without implicit handshaking dialogues for providing reliability, ordering, or data integrity. Thus, UDP provides an unreliable service and datagrams may arrive out of order, appear duplicated, or go missing without notice. http://en.wikipedia.org/wiki/User_Datagram_Protocol.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type PacketObj:TCPType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
TCP provides reliable, ordered delivery of a stream of bytes from a program on one computer to another program on another computer. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
Diagram
Diagram Network_Packet_Object_xsd.tmp#TCPType_TCP_Header Network_Packet_Object_xsd.tmp#TCPType_Options Network_Packet_Object_xsd.tmp#TCPType_Data
Used by
Children PacketObj:Data, PacketObj:Options, PacketObj:TCP_Header
Source
 
<xs:complexType name="TCPType">
  <xs:annotation>
    <xs:documentation>TCP provides reliable, ordered delivery of a stream of bytes from a program on one computer to another program on another computer. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="TCP_Header" type="PacketObj:TCPHeaderType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The TCP header contains 10 mandatory fields and an optional extension field. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Options" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Options have up to three fields: Option-Kind (1 byte), Option-Length (1 byte), Option-Data (variable). This field will be further defined when required.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Data" type="cyboxCommon:DataSegmentType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The Data field specifies the data payload of the TCP packet.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:TCPHeaderType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The TCP header contains 10 mandatory fields and an optional extension field. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
Diagram
Diagram Network_Packet_Object_xsd.tmp#TCPHeaderType_Src_Port Network_Packet_Object_xsd.tmp#TCPHeaderType_Dest_Port Network_Packet_Object_xsd.tmp#TCPHeaderType_Seq_Num Network_Packet_Object_xsd.tmp#TCPHeaderType_ACK_Num Network_Packet_Object_xsd.tmp#TCPHeaderType_Data_Offset Network_Packet_Object_xsd.tmp#TCPHeaderType_Reserved Network_Packet_Object_xsd.tmp#TCPHeaderType_TCP_Flags Network_Packet_Object_xsd.tmp#TCPHeaderType_Window Network_Packet_Object_xsd.tmp#TCPHeaderType_Checksum Network_Packet_Object_xsd.tmp#TCPHeaderType_Urg_Ptr
Used by
Children PacketObj:ACK_Num, PacketObj:Checksum, PacketObj:Data_Offset, PacketObj:Dest_Port, PacketObj:Reserved, PacketObj:Seq_Num, PacketObj:Src_Port, PacketObj:TCP_Flags, PacketObj:Urg_Ptr, PacketObj:Window
Source
 
<xs:complexType name="TCPHeaderType">
  <xs:annotation>
    <xs:documentation>The TCP header contains 10 mandatory fields and an optional extension field. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Src_Port" type="PortObj:PortObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Identifies the sending port.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Dest_Port" type="PortObj:PortObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Identifies the receiving port.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Seq_Num" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The Sequence number (32-bits) has a dual role: If the SYN flag is set, then this is the initial sequence numbers. If the SYN flag is clear (see Control Bits element), then this is the accumulated sequence number of the first data byte of this packet for the current session. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="ACK_Num" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>If the ACK flag (see Control Bits element) is set then the value of this field is the next sequence number that the receiver is expecting.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Data_Offset" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Specifies the size of the TCP header in 32-bit words.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Reserved" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>these 3 bits are reserved for future use and should be set to zero.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="TCP_Flags" type="PacketObj:TCPFlagsType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The TCP header contains 9 flags (aka Control Bits).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Window" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The size of the receive window, which specifies the number of bytes (beyond the sequence number in the acknowledgment field) that the sender of this segment is currently willing to receive. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Checksum" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The 16-bit checksum field is used for error-checking of the header and data. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Urg_Ptr" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>If the URG flag is set, then this 16-bit field is an offset from the sequence number indicating the last urgent data byte. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:TCPFlagsType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Defines the 9 different flags in the TCP header.
Diagram
Diagram Network_Packet_Object_xsd.tmp#TCPFlagsType_ns Network_Packet_Object_xsd.tmp#TCPFlagsType_cwr Network_Packet_Object_xsd.tmp#TCPFlagsType_ece Network_Packet_Object_xsd.tmp#TCPFlagsType_urg Network_Packet_Object_xsd.tmp#TCPFlagsType_ack Network_Packet_Object_xsd.tmp#TCPFlagsType_psh Network_Packet_Object_xsd.tmp#TCPFlagsType_rst Network_Packet_Object_xsd.tmp#TCPFlagsType_syn Network_Packet_Object_xsd.tmp#TCPFlagsType_fin
Used by
Attributes
QName Type Use Annotation
ack xs:boolean optional 
indicates that the Acknowledgment field is significant. All packets after the initial SYN packet sent by the client should have this flag set. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
cwr xs:boolean optional 
Congestion Window Reduced (CWR) flag is set by the sending host to indicate that it received a TCP segment with the ECE flag set and had responded in congestion control mechanism. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
ece xs:boolean optional 
ECN-Echo indicates: if the SYN flag is set, that the TCP peer is ECN capable; if the SYN flag is clear, that a packet with Congestion Experienced flag in IP header set is received during normal transmission. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
fin xs:boolean optional 
If this flag is set, it means there is no more data from sender.
ns xs:boolean optional 
ECN-nonce concealment protection.
psh xs:boolean optional 
Push functions. asks to push the buffered dtata to the receiving application. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
rst xs:boolean optional 
Reset the connection.
syn xs:boolean optional 
Synchronize sequence numbers. Only the first packet sent from each end should have this flag set. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
urg xs:boolean optional 
Indicates that the Urgent point field is significant.
Source
 
<xs:complexType name="TCPFlagsType">
  <xs:annotation>
    <xs:documentation>Defines the 9 different flags in the TCP header.</xs:documentation>
  </xs:annotation>
  <xs:attribute name="ns" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>ECN-nonce concealment protection.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="cwr" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>Congestion Window Reduced (CWR) flag is set by the sending host to indicate that it received a TCP segment with the ECE flag set and had responded in congestion control mechanism. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="ece" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>ECN-Echo indicates: if the SYN flag is set, that the TCP peer is ECN capable; if the SYN flag is clear, that a packet with Congestion Experienced flag in IP header set is received during normal transmission. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="urg" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>Indicates that the Urgent point field is significant.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="ack" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>indicates that the Acknowledgment field is significant. All packets after the initial SYN packet sent by the client should have this flag set. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="psh" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>Push functions. asks to push the buffered dtata to the receiving application. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="rst" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>Reset the connection.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="syn" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>Synchronize sequence numbers. Only the first packet sent from each end should have this flag set. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="fin" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>If this flag is set, it means there is no more data from sender.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>
Complex Type PacketObj:UDPType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
UDP uses a simple transmission model without implicit handshaking dialogues for providing reliability, ordering, or data integrity. Thus, UDP provides an unreliable service and datagrams may arrive out of order, appear duplicated, or go missing without notice. http://en.wikipedia.org/wiki/User_Datagram_Protocol.
Diagram
Diagram Network_Packet_Object_xsd.tmp#UDPType_UDP_Header Network_Packet_Object_xsd.tmp#UDPType_Data
Used by
Children PacketObj:Data, PacketObj:UDP_Header
Source
 
<xs:complexType name="UDPType">
  <xs:annotation>
    <xs:documentation>UDP uses a simple transmission model without implicit handshaking dialogues for providing reliability, ordering, or data integrity. Thus, UDP provides an unreliable service and datagrams may arrive out of order, appear duplicated, or go missing without notice. http://en.wikipedia.org/wiki/User_Datagram_Protocol.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="UDP_Header" type="PacketObj:UDPHeaderType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The UDP header consists of four fields, which are defined here.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Data" type="cyboxCommon:DataSegmentType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The Data field specifies the data payload of the UDP packet.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type PacketObj:UDPHeaderType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The UDP header type defines the four fields in the UDP header.
Diagram
Diagram Network_Packet_Object_xsd.tmp#UDPHeaderType_SrcPort Network_Packet_Object_xsd.tmp#UDPHeaderType_DestPort Network_Packet_Object_xsd.tmp#UDPHeaderType_Length Network_Packet_Object_xsd.tmp#UDPHeaderType_Checksum
Used by
Children PacketObj:Checksum, PacketObj:DestPort, PacketObj:Length, PacketObj:SrcPort
Source
 
<xs:complexType name="UDPHeaderType">
  <xs:annotation>
    <xs:documentation>The UDP header type defines the four fields in the UDP header.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="SrcPort" type="PortObj:PortObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Identifies the sender's port.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="DestPort" type="PortObj:PortObjectType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Identifies the receiver's port.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Length" type="cyboxCommon:IntegerObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Specifies the length in bytes of the entire datagram (header and data).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Checksum" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The checksum is used for error-checking of the header and data.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Simple Type PacketObj:ARPOpTypeEnum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
ARPOpTypeEnum contains the various ARP Operation Types.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration ARP request(1) 
Indicates the ARP request operation, or value 1 in the OPER field of an ARP packet.
enumeration ARP reply(2) 
Indicates the ARP reply operation, or value 2 in the OPER field of an ARP packet.
enumeration RARP request(3) 
Indicates the RARP request operation, or value 3 in the OPER field of an ARP packet.
enumeration RARP reply(4) 
Indicates the RARP reply operation, or value 4 in the OPER field of an ARP packet.
Source
 
<xs:simpleType name="ARPOpTypeEnum">
  <xs:annotation>
    <xs:documentation>ARPOpTypeEnum contains the various ARP Operation Types.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="ARP request(1)">
      <xs:annotation>
        <xs:documentation>Indicates the ARP request operation, or value 1 in the OPER field of an ARP packet.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="ARP reply(2)">
      <xs:annotation>
        <xs:documentation>Indicates the ARP reply operation, or value 2 in the OPER field of an ARP packet.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="RARP request(3)">
      <xs:annotation>
        <xs:documentation>Indicates the RARP request operation, or value 3 in the OPER field of an ARP packet.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="RARP reply(4)">
      <xs:annotation>
        <xs:documentation>Indicates the RARP reply operation, or value 4 in the OPER field of an ARP packet.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
Simple Type PacketObj:DoNotFragmentTypeEnum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This type enumerates the meaning of the Do Not Fragment bit used in IPv4 flags.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration fragementifnecessary(0) 
Indicates that the router or other device should fragment the packet if necessary, especially if the packet size is bigger than the MTU of an outgoing interface.
enumeration donotfragment(1) 
Indicates that the router or other device should NOT fragment the packet in any circumstance.
Source
 
<xs:simpleType name="DoNotFragmentTypeEnum">
  <xs:annotation>
    <xs:documentation>This type enumerates the meaning of the Do Not Fragment bit used in IPv4 flags.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="fragementifnecessary(0)">
      <xs:annotation>
        <xs:documentation>Indicates that the router or other device should fragment the packet if necessary, especially if the packet size is bigger than the MTU of an outgoing interface.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="donotfragment(1)">
      <xs:annotation>
        <xs:documentation>Indicates that the router or other device should NOT fragment the packet in any circumstance.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
Simple Type PacketObj:MoreFragmentsTypeEnum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This type enumerates the meaning of the More Fragments bit used in IPv4 flags.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration lastfragment(0) 
Indicates that the last fragment has been received. In other words, the "more fragments" flag is set to 0.
enumeration morefragmentstofollow(1) 
Indicates that more fragments need to be received. In other words, the "more fragments" flag is set.
Source
 
<xs:simpleType name="MoreFragmentsTypeEnum">
  <xs:annotation>
    <xs:documentation>This type enumerates the meaning of the More Fragments bit used in IPv4 flags.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="lastfragment(0)">
      <xs:annotation>
        <xs:documentation>Indicates that the last fragment has been received. In other words, the "more fragments" flag is set to 0.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="morefragmentstofollow(1)">
      <xs:annotation>
        <xs:documentation>Indicates that more fragments need to be received. In other words, the "more fragments" flag is set.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
Simple Type PacketObj:IPv4CopyFlagTypeEnum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The copy flag indicates whether the option is copied into all fragments on fragmentation (0=not copied; 1=copied). This information is also captured in the IPv4OptionsTypeEnum which lists all options, which incorporates copy and class numbers.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration donotcopy(0) 
Indicates that the options need NOT be copied into all fragments of a fragmented packet.
enumeration copy(1) 
Indicates that the options need to be copied into all fragments of a fragmented packet.
Source
 
<xs:simpleType name="IPv4CopyFlagTypeEnum">
  <xs:annotation>
    <xs:documentation>The copy flag indicates whether the option is copied into all fragments on fragmentation (0=not copied; 1=copied). This information is also captured in the IPv4OptionsTypeEnum which lists all options, which incorporates copy and class numbers.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="donotcopy(0)">
      <xs:annotation>
        <xs:documentation>Indicates that the options need NOT be copied into all fragments of a fragmented packet.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="copy(1)">
      <xs:annotation>
        <xs:documentation>Indicates that the options need to be copied into all fragments of a fragmented packet.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
Simple Type PacketObj:IPv4ClassTypeEnum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The option class is represented by 2 bits. The explicit meanings are captured here in an enumerated list. This information is also captured in the IPv4OptionsTypeEnum which lists all options, which incorporates copy and class numbers.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration control(0) 
Indicates the "control" options.
enumeration reserved(1) 
Indicates a reserved value.
enumeration debuggingandmeasurement(2) 
Indicates the debugging and measurement options.
enumeration reserved(3) 
Indicates a reserved value.
Source
 
<xs:simpleType name="IPv4ClassTypeEnum">
  <xs:annotation>
    <xs:documentation>The option class is represented by 2 bits. The explicit meanings are captured here in an enumerated list. This information is also captured in the IPv4OptionsTypeEnum which lists all options, which incorporates copy and class numbers.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="control(0)">
      <xs:annotation>
        <xs:documentation>Indicates the "control" options.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="reserved(1)">
      <xs:annotation>
        <xs:documentation>Indicates a reserved value.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="debuggingandmeasurement(2)">
      <xs:annotation>
        <xs:documentation>Indicates the debugging and measurement options.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="reserved(3)">
      <xs:annotation>
        <xs:documentation>Indicates a reserved value.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
Simple Type PacketObj:IPv4OptionsTypeEnum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
The Internet Protocol (IP) has provision for optional header fields identified by an option type field. Options 0 and 1 are exactly one octet which is their type field. All other options have their one octet type field, followed by a one octet length field, followed by length-2 octets of option data. The option type field is sub-divided into a one bit copied flag, a two bit class field, and a five bit option number. These taken together form an eight bit value for the option type field. IP options are commonly referred to by this value. The IPv4OptionsEnum enumerates the options numbers that can be applied in IP. See http://www.iana.org/assignments/ip-parameters for more information.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration endofoptionslist(0) 
Indicates the End of Options List option, or EOOL.
enumeration nop(1) 
Indicates the No Operation option, or NOP.
enumeration security(2) 
Indicates the Security option, or SEC.
enumeration loosesourceroute(3) 
Indicates the Loose Source Route option, or LSR.
enumeration timestamp(4) 
Indicates the Time Stamp option, or TS.
enumeration extendedsecurity(5) 
Indicates the Extended Security option, or E-SEC.
enumeration commercialsecurity(6) 
Indicates the Commercial Security option, or CIPSO.
enumeration recordroute(7) 
Indicates the Record Route option, or RR.
enumeration streamidentifier(8) 
Indicates the Stream ID option, or SID.
enumeration strictsourceroute(9) 
Indicates the Strict Source Route option, or SSR.
enumeration experimentalmeasure(10) 
Indicates the Experimental Measurement option, or ZSU.
enumeration mtuprobe(11) 
Indicates the MTU probe option, or MTUP.
enumeration mtureply(12) 
Indicates the MTU reply option, or MTUR.
enumeration experimentalflowcontrol(13) 
Indicates the Experimental Flow Control option, or FINN.
enumeration experimentalaccesscontrol(14) 
Indicates the Experimental Access Control option, or FINN.
enumeration encode(15)
enumeration imitrafficdescriptor(16) 
Indicates the IMI Traffic Descriptor option, or IMITD.
enumeration extendedip(17) 
Indicates the Extended Internet Protocol option, or EIP.
enumeration traceroute(18) 
Indicates the Trace Route option, or TR.
enumeration addressextension(19) 
Indicates the Address Extension option, or ADDEXT.
enumeration routeralert(20) 
Indicates a Router Alert option, or RTRALT.
enumeration selectivedirectedbroadcasemode(21) 
Indicates a Selective Directed Broadcast option, or SDB.
enumeration dynamicepacketstate(23) 
Indicates the Dynamic Packet State option, or DPS.
enumeration upstreammulticastpacket(24) 
Indicates the Upstream Multicast Packet option, or UMP.
enumeration quickstart(25) 
Indicates the Quick-Start option, or QS.
enumeration exp(30) 
Indicates the RFC3692-style Experiment option, or EXP.
Source
 
<xs:simpleType name="IPv4OptionsTypeEnum">
  <xs:annotation>
    <xs:documentation>The Internet Protocol (IP) has provision for optional header fields identified by an option type field. Options 0 and 1 are exactly one octet which is their type field. All other options have their one octet type field, followed by a one octet length field, followed by length-2 octets of option data. The option type field is sub-divided into a one bit copied flag, a two bit class field, and a five bit option number. These taken together form an eight bit value for the option type field. IP options are commonly referred to by this value. The IPv4OptionsEnum enumerates the options numbers that can be applied in IP. See http://www.iana.org/assignments/ip-parameters for more information.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="endofoptionslist(0)">
      <xs:annotation>
        <xs:documentation>Indicates the End of Options List option, or EOOL.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="nop(1)">
      <xs:annotation>
        <xs:documentation>Indicates the No Operation option, or NOP.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="security(2)">
      <xs:annotation>
        <xs:documentation>Indicates the Security option, or SEC.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="loosesourceroute(3)">
      <xs:annotation>
        <xs:documentation>Indicates the Loose Source Route option, or LSR.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="timestamp(4)">
      <xs:annotation>
        <xs:documentation>Indicates the Time Stamp option, or TS.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="extendedsecurity(5)">
      <xs:annotation>
        <xs:documentation>Indicates the Extended Security option, or E-SEC.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="commercialsecurity(6)">
      <xs:annotation>
        <xs:documentation>Indicates the Commercial Security option, or CIPSO.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="recordroute(7)">
      <xs:annotation>
        <xs:documentation>Indicates the Record Route option, or RR.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="streamidentifier(8)">
      <xs:annotation>
        <xs:documentation>Indicates the Stream ID option, or SID.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="strictsourceroute(9)">
      <xs:annotation>
        <xs:documentation>Indicates the Strict Source Route option, or SSR.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="experimentalmeasure(10)">
      <xs:annotation>
        <xs:documentation>Indicates the Experimental Measurement option, or ZSU.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="mtuprobe(11)">
      <xs:annotation>
        <xs:documentation>Indicates the MTU probe option, or MTUP.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="mtureply(12)">
      <xs:annotation>
        <xs:documentation>Indicates the MTU reply option, or MTUR.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="experimentalflowcontrol(13)">
      <xs:annotation>
        <xs:documentation>Indicates the Experimental Flow Control option, or FINN.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="experimentalaccesscontrol(14)">
      <xs:annotation>
        <xs:documentation>Indicates the Experimental Access Control option, or FINN.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="encode(15)">
      <xs:annotation>
        <xs:documentation/>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="imitrafficdescriptor(16)">
      <xs:annotation>
        <xs:documentation>Indicates the IMI Traffic Descriptor option, or IMITD.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="extendedip(17)">
      <xs:annotation>
        <xs:documentation>Indicates the Extended Internet Protocol option, or EIP.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="traceroute(18)">
      <xs:annotation>
        <xs:documentation>Indicates the Trace Route option, or TR.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="addressextension(19)">
      <xs:annotation>
        <xs:documentation>Indicates the Address Extension option, or ADDEXT.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="routeralert(20)">
      <xs:annotation>
        <xs:documentation>Indicates a Router Alert option, or RTRALT.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="selectivedirectedbroadcasemode(21)">
      <xs:annotation>
        <xs:documentation>Indicates a Selective Directed Broadcast option, or SDB.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="dynamicepacketstate(23)">
      <xs:annotation>
        <xs:documentation>Indicates the Dynamic Packet State option, or DPS.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="upstreammulticastpacket(24)">
      <xs:annotation>
        <xs:documentation>Indicates the Upstream Multicast Packet option, or UMP.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="quickstart(25)">
      <xs:annotation>
        <xs:documentation>Indicates the Quick-Start option, or QS.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="exp(30)">
      <xs:annotation>
        <xs:documentation>Indicates the RFC3692-style Experiment option, or EXP.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
Simple Type PacketObj:IPv6DoNotRecogActionTypeEnum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Enumerates possible actions when an option is not recognized.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration skipoption(00) 
Indicates that the option should be skipped and the header should continue to be processed. See RFC 2460.
enumeration discardpacket(01) 
Indicates that the packet should be discarded. See RFC 2460.
enumeration discardpacketsendicmpcode2(10) 
Indicates that the packet should be discarded and regardless of whether or not the packet's Destination Address was a multicast address, send an ICMP Parameter Problem, Code 2, message to the packet's Source Address, pointing to the unrecognized Option Type. See RFC 2460.
enumeration discardpacketsendicmpcode2nomulti(11) 
Indicates that the packet should be discarded and only if the packet's Destination Address was not a multicast address, send an ICMP Parameter Problem, Code 2, message to the packet's Source Address, pointing to the unrecognized Option Type. See RFC 2460.
Source
 
<xs:simpleType name="IPv6DoNotRecogActionTypeEnum">
  <xs:annotation>
    <xs:documentation>Enumerates possible actions when an option is not recognized.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="skipoption(00)">
      <xs:annotation>
        <xs:documentation>Indicates that the option should be skipped and the header should continue to be processed. See RFC 2460.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="discardpacket(01)">
      <xs:annotation>
        <xs:documentation>Indicates that the packet should be discarded. See RFC 2460.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="discardpacketsendicmpcode2(10)">
      <xs:annotation>
        <xs:documentation>Indicates that the packet should be discarded and regardless of whether or not the packet's Destination Address was a multicast address, send an ICMP Parameter Problem, Code 2, message to the packet's Source Address, pointing to the unrecognized Option Type. See RFC 2460.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="discardpacketsendicmpcode2nomulti(11)">
      <xs:annotation>
        <xs:documentation>Indicates that the packet should be discarded and only if the packet's Destination Address was not a multicast address, send an ICMP Parameter Problem, Code 2, message to the packet's Source Address, pointing to the unrecognized Option Type. See RFC 2460.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
Simple Type PacketObj:IPv6PacketChangeTypeEnum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Enumerated list that specifies whether or not the Option Data of an option can change en-route to the packet's final destination.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration nochange(0) 
Indicates that the packet does not change en-route. See RFC 2460.
enumeration change(1) 
Indicates that the packet may change en-route. See RFC 2460.
Source
 
<xs:simpleType name="IPv6PacketChangeTypeEnum">
  <xs:annotation>
    <xs:documentation>Enumerated list that specifies whether or not the Option Data of an option can change en-route to the packet's final destination.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="nochange(0)">
      <xs:annotation>
        <xs:documentation>Indicates that the packet does not change en-route. See RFC 2460.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="change(1)">
      <xs:annotation>
        <xs:documentation>Indicates that the packet may change en-route. See RFC 2460.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
Simple Type PacketObj:IPVersionTypeEnum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Enumerates the different Internet Protocol versions. IPv4(4) and IPv6(6) are the most common.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration IPv4(4) 
Indicates IP Version 4.
enumeration ST(5) 
Indicates the IP version designating ST Datagram Mode.
enumeration IPv6(6) 
Indicates IP Version 6.
enumeration TP/IX(7) 
Indicates the IP version designating TP/IX: The Next Internet.
enumeration PIP(8) 
Indicates the IP version designating PIP: The P Internet Protocol.
enumeration TUBA(9) 
Indicates the IP version designating TUBA (TCP and UDP with Bigger Addresses, i.e. RFC 1347).
Source
 
<xs:simpleType name="IPVersionTypeEnum">
  <xs:annotation>
    <xs:documentation>Enumerates the different Internet Protocol versions. IPv4(4) and IPv6(6) are the most common.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="IPv4(4)">
      <xs:annotation>
        <xs:documentation>Indicates IP Version 4.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="ST(5)">
      <xs:annotation>
        <xs:documentation>Indicates the IP version designating ST Datagram Mode.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="IPv6(6)">
      <xs:annotation>
        <xs:documentation>Indicates IP Version 6.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="TP/IX(7)">
      <xs:annotation>
        <xs:documentation>Indicates the IP version designating TP/IX: The Next Internet.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="PIP(8)">
      <xs:annotation>
        <xs:documentation>Indicates the IP version designating PIP: The P Internet Protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="TUBA(9)">
      <xs:annotation>
        <xs:documentation>Indicates the IP version designating TUBA (TCP and UDP with Bigger Addresses, i.e. RFC 1347).</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
Simple Type PacketObj:IANAHardwareTypeEnum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
This enumerated type specifies Address Resolution Protocol (ARP) parameters. http://www.iana.org/assignments/arp-parameters/arp-parameters.xml.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Ethernet(1) 
Indicates Ethernet hardware.
enumeration IEEE802(6) 
Indicates IEEE 802 compliant hardware for networks carrying variable-size packets.
enumeration ARCNET(7) 
Indicates the ARCNET LAN protocol.
enumeration FrameRelay(15) 
Indicates the Frame Relay WAN technology.
enumeration ATM(16) 
Indicates the ATM (Asynchronous Transfer Mode) networking standard.
enumeration HDLC(17) 
Indicates the HDLC (High-Level Data Link Control) protocol.
enumeration FibreChannel(18) 
Indicates the FibreChannel technology.
enumeration ATM(19) 
Indicates the ATM (Asynchronous Transfer Mode) networking standard.
enumeration SerialLine(20) 
Indicates the Serial Line protocol, or SLIP.
Source
 
<xs:simpleType name="IANAHardwareTypeEnum">
  <xs:annotation>
    <xs:documentation>This enumerated type specifies Address Resolution Protocol (ARP) parameters. http://www.iana.org/assignments/arp-parameters/arp-parameters.xml.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="Ethernet(1)">
      <xs:annotation>
        <xs:documentation>Indicates Ethernet hardware.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="IEEE802(6)">
      <xs:annotation>
        <xs:documentation>Indicates IEEE 802 compliant hardware for networks carrying variable-size packets.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="ARCNET(7)">
      <xs:annotation>
        <xs:documentation>Indicates the ARCNET LAN protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="FrameRelay(15)">
      <xs:annotation>
        <xs:documentation>Indicates the Frame Relay WAN technology.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="ATM(16)">
      <xs:annotation>
        <xs:documentation>Indicates the ATM (Asynchronous Transfer Mode) networking standard.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="HDLC(17)">
      <xs:annotation>
        <xs:documentation>Indicates the HDLC (High-Level Data Link Control) protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="FibreChannel(18)">
      <xs:annotation>
        <xs:documentation>Indicates the FibreChannel technology.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="ATM(19)">
      <xs:annotation>
        <xs:documentation>Indicates the ATM (Asynchronous Transfer Mode) networking standard.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="SerialLine(20)">
      <xs:annotation>
        <xs:documentation>Indicates the Serial Line protocol, or SLIP.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
Simple Type PacketObj:IANAEtherTypeEnum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
http://cavebear.com/archive/cavebear/Ethernet/type.html http://www.iana.org/assignments/ethernet-numbers http://standards.ieee.org/develop/regauth/ethertype/eth.txt http://en.wikipedia.org/wiki/EtherType.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration IPv4(0x0800) 
Indicates the IPv4 Ethernet type is specified.
enumeration ARP(0x0806) 
Indicates the ARP Ethernet type is specified.
enumeration RARP(0x8035) 
Indicates the RARP Ethernet type is specified.
enumeration IPX(0x8137) 
Indicates the IPX Ethernet type is specified.
enumeration SNMP(0x814C) 
Indicates the SNMP Ethernet type is specified.
enumeration IPv6(0x86DD) 
Indicates the IPv6 Ethernet type is specified.
Source
 
<xs:simpleType name="IANAEtherTypeEnum">
  <xs:annotation>
    <xs:documentation>http://cavebear.com/archive/cavebear/Ethernet/type.html http://www.iana.org/assignments/ethernet-numbers http://standards.ieee.org/develop/regauth/ethertype/eth.txt http://en.wikipedia.org/wiki/EtherType.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="IPv4(0x0800)">
      <xs:annotation>
        <xs:documentation>Indicates the IPv4 Ethernet type is specified.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="ARP(0x0806)">
      <xs:annotation>
        <xs:documentation>Indicates the ARP Ethernet type is specified.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="RARP(0x8035)">
      <xs:annotation>
        <xs:documentation>Indicates the RARP Ethernet type is specified.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="IPX(0x8137)">
      <xs:annotation>
        <xs:documentation>Indicates the IPX Ethernet type is specified.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="SNMP(0x814C)">
      <xs:annotation>
        <xs:documentation>Indicates the SNMP Ethernet type is specified.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="IPv6(0x86DD)">
      <xs:annotation>
        <xs:documentation>Indicates the IPv6 Ethernet type is specified.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
Simple Type PacketObj:IANAAssignedIPNumbersTypeEnum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Assigned Internet Protocol Numbers http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml List of protocol numbers used in the Protocol fields of the IPv4 header and the Next Header of the IPv6 header.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration IPv6hopbyhop(0) 
Indicates the IPv6 Hop-By-Hop option protocol (HOPOPT).
enumeration ICMP(1) 
Indicates the Internet Control Message protocol (HOPOPT).
enumeration IGMP(2) 
Indicates the Internet Control Message protocol (HOPOPT).
enumeration GGP(3) 
Indicates the Gateway-to-Gateway protocol (HOPOPT).
enumeration IPv4Encapsulation(4) 
Indicates the IPv4 Encapsulation protocol (IPv4).
enumeration ST(5) 
Indicates the Stream protocol (HOPOPT).
enumeration TCP(6) 
Indicates the TCP protocol.
enumeration EGP(8) 
Indicates the EGP (Exterior Gateway) protocol.
enumeration IGRP(9) 
Indicates the IGP/IGRP (Cisco) protocol.
enumeration NVP(11) 
Indicates the Network-Voice protocol.
enumeration PUP(12) 
Indicates the PUP protocol.
enumeration ARGUS(13) 
Indicates the ARGUS protocol.
enumeration EMCON(14) 
Indicates the EMCON protocol.
enumeration XNET(15) 
Indicates the Cross Net Debugger protocol.
enumeration UDP(17) 
Indicates the UDP protocol.
enumeration IPv6Encapsulation(41) 
Indicates the IPv6 protocol.
enumeration SDRP(42) 
Indicates the Source Demand Routing protocol.
enumeration IPv6routingheader(43) 
Indicates the routing header for IPv6.
enumeration IPv6fragmentheader(44) 
Indicates the fragment header for IPv6.
enumeration RSVP(46) 
Indicates the Reservation Protocol.
enumeration GRE(47) 
Indicates the General Routing Encapsulation protocol number.
enumeration encapsultaesecuritypayload_ESP(50) 
Indicates the Encapsulated Security Payload protocol number.
enumeration authenticationheader_AH(51) 
Indicates the Authentication Header protocol number.
enumeration ICMPv6(58) 
Indicates the ICMP for v6 protocol number.
enumeration IPv6nonextheader(59) 
Indicates the No Next Header for IPv6 protocol number.
enumeration IPv6destinationoptions(60) 
Indicates the Destination Options for IPv6 protocol number.
enumeration mobilityheader(135) 
Indicates the Mobility Header protocol number.
Source
 
<xs:simpleType name="IANAAssignedIPNumbersTypeEnum">
  <xs:annotation>
    <xs:documentation>Assigned Internet Protocol Numbers http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml List of protocol numbers used in the Protocol fields of the IPv4 header and the Next Header of the IPv6 header.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="IPv6hopbyhop(0)">
      <xs:annotation>
        <xs:documentation>Indicates the IPv6 Hop-By-Hop option protocol (HOPOPT).</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="ICMP(1)">
      <xs:annotation>
        <xs:documentation>Indicates the Internet Control Message protocol (HOPOPT).</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="IGMP(2)">
      <xs:annotation>
        <xs:documentation>Indicates the Internet Control Message protocol (HOPOPT).</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="GGP(3)">
      <xs:annotation>
        <xs:documentation>Indicates the Gateway-to-Gateway protocol (HOPOPT).</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="IPv4Encapsulation(4)">
      <xs:annotation>
        <xs:documentation>Indicates the IPv4 Encapsulation protocol (IPv4).</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="ST(5)">
      <xs:annotation>
        <xs:documentation>Indicates the Stream protocol (HOPOPT).</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="TCP(6)">
      <xs:annotation>
        <xs:documentation>Indicates the TCP protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="EGP(8)">
      <xs:annotation>
        <xs:documentation>Indicates the EGP (Exterior Gateway) protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="IGRP(9)">
      <xs:annotation>
        <xs:documentation>Indicates the IGP/IGRP (Cisco) protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="NVP(11)">
      <xs:annotation>
        <xs:documentation>Indicates the Network-Voice protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="PUP(12)">
      <xs:annotation>
        <xs:documentation>Indicates the PUP protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="ARGUS(13)">
      <xs:annotation>
        <xs:documentation>Indicates the ARGUS protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="EMCON(14)">
      <xs:annotation>
        <xs:documentation>Indicates the EMCON protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="XNET(15)">
      <xs:annotation>
        <xs:documentation>Indicates the Cross Net Debugger protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="UDP(17)">
      <xs:annotation>
        <xs:documentation>Indicates the UDP protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="IPv6Encapsulation(41)">
      <xs:annotation>
        <xs:documentation>Indicates the IPv6 protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="SDRP(42)">
      <xs:annotation>
        <xs:documentation>Indicates the Source Demand Routing protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="IPv6routingheader(43)">
      <xs:annotation>
        <xs:documentation>Indicates the routing header for IPv6.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="IPv6fragmentheader(44)">
      <xs:annotation>
        <xs:documentation>Indicates the fragment header for IPv6.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="RSVP(46)">
      <xs:annotation>
        <xs:documentation>Indicates the Reservation Protocol.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="GRE(47)">
      <xs:annotation>
        <xs:documentation>Indicates the General Routing Encapsulation protocol number.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="encapsultaesecuritypayload_ESP(50)">
      <xs:annotation>
        <xs:documentation>Indicates the Encapsulated Security Payload protocol number.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="authenticationheader_AH(51)">
      <xs:annotation>
        <xs:documentation>Indicates the Authentication Header protocol number.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="ICMPv6(58)">
      <xs:annotation>
        <xs:documentation>Indicates the ICMP for v6 protocol number.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="IPv6nonextheader(59)">
      <xs:annotation>
        <xs:documentation>Indicates the No Next Header for IPv6 protocol number.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="IPv6destinationoptions(60)">
      <xs:annotation>
        <xs:documentation>Indicates the Destination Options for IPv6 protocol number.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="mobilityheader(135)">
      <xs:annotation>
        <xs:documentation>Indicates the Mobility Header protocol number.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
Complex Type PacketObj:IANAPortNumberRegistryType
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
IANAPortNumberRegistryType specifies port numbers, via a union of the IANAPortNumberRegistryTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.
Diagram
Diagram Network_Packet_Object_xsd.tmp#IANAPortNumberRegistryType_datatype
Type restriction of BaseObjectPropertyType
Type hierarchy
Source
 
<xs:complexType name="IANAPortNumberRegistryType">
  <xs:annotation>
    <xs:documentation>IANAPortNumberRegistryType specifies port numbers, via a union of the IANAPortNumberRegistryTypeEnum type and the atomic xs:string type. Its base type is the BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:restriction base="cyboxCommon:BaseObjectPropertyType">
      <xs:simpleType>
        <xs:union memberTypes="PacketObj:IANAPortNumberRegistryTypeEnum xs:string"/>
      </xs:simpleType>
      <xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
        <xs:annotation>
          <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
  </xs:simpleContent>
</xs:complexType>
Simple Type PacketObj:IANAPortNumberRegistryTypeEnum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration ftpdata(20) 
Indicates the port for ftpdata.
enumeration ftp(21) 
Indicates the port for ftp.
enumeration ssh(22) 
Indicates the port for ssh.
enumeration telnet(23) 
Indicates the port for telnet.
enumeration smtp(25) 
Indicates the port for smtp.
enumeration domain(53) 
Indicates the domain port.
enumeration tftp(69) 
Indicates the port for tftp.
enumeration http(80) 
Indicates the port for http.
enumeration ldap(389) 
Indicates the port for ldap.
enumeration https(443) 
Indicates the port for https.
Source
 
<xs:simpleType name="IANAPortNumberRegistryTypeEnum">
  <xs:annotation>
    <xs:documentation>http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="ftpdata(20)">
      <xs:annotation>
        <xs:documentation>Indicates the port for ftpdata.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="ftp(21)">
      <xs:annotation>
        <xs:documentation>Indicates the port for ftp.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="ssh(22)">
      <xs:annotation>
        <xs:documentation>Indicates the port for ssh.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="telnet(23)">
      <xs:annotation>
        <xs:documentation>Indicates the port for telnet.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="smtp(25)">
      <xs:annotation>
        <xs:documentation>Indicates the port for smtp.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="domain(53)">
      <xs:annotation>
        <xs:documentation>Indicates the domain port.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="tftp(69)">
      <xs:annotation>
        <xs:documentation>Indicates the port for tftp.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="http(80)">
      <xs:annotation>
        <xs:documentation>Indicates the port for http.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="ldap(389)">
      <xs:annotation>
        <xs:documentation>Indicates the port for ldap.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="https(443)">
      <xs:annotation>
        <xs:documentation>Indicates the port for https.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
Simple Type PacketObj:MFlagTypeEnum
Namespace http://cybox.mitre.org/objects#PacketObject-2
Annotations
 
Used by the IPv6 Fragment Header to indicate whether or not there are more fragments.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration lastfragment(0) 
Fragment is the last fragment.
enumeration morefragments(1) 
There are more fragments (current is not the last).
Source
 
<xs:simpleType name="MFlagTypeEnum">
  <xs:annotation>
    <xs:documentation>Used by the IPv6 Fragment Header to indicate whether or not there are more fragments.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="lastfragment(0)">
      <xs:annotation>
        <xs:documentation>Fragment is the last fragment.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="morefragments(1)">
      <xs:annotation>
        <xs:documentation>There are more fragments (current is not the last).</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
Attribute PacketObj:IANAEtherType / @datatype
Namespace No namespace
Annotations
 
This attribute is optional and specifies the expected type for the value of the specified property.
Type DatatypeEnum
Used by
Source
 
<xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
  <xs:annotation>
    <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:IANAHardwareType / @datatype
Namespace No namespace
Annotations
 
This attribute is optional and specifies the expected type for the value of the specified property.
Type DatatypeEnum
Used by
Source
 
<xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
  <xs:annotation>
    <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:ARPOpType / @datatype
Namespace No namespace
Annotations
 
This attribute is optional and specifies the expected type for the value of the specified property.
Type DatatypeEnum
Used by
Complex Type PacketObj:ARPOpType
Source
 
<xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
  <xs:annotation>
    <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:NDPPrefixInfoType / @link_flag
Namespace No namespace
Annotations
Type xs:boolean
Used by
Source
Attribute PacketObj:NDPPrefixInfoType / @addr_config_flag
Namespace No namespace
Annotations
 
1-bit autonomous address-configuration flag. When set indicates that this prefix can be usd for stateless address configuration.
Type xs:boolean
Used by
Source
 
<xs:attribute name="addr_config_flag" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>1-bit autonomous address-configuration flag. When set indicates that this prefix can be usd for stateless address configuration.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:RouterAdvertisementType / @managed_address_config_flag
Namespace No namespace
Annotations
 
1-bit "Managed address configuration" flag. When set, it indicates that addresses are available via Dynamic Host Configuration Protocol. If the M flag is set, the O flag is redundant and can be ignored because DHCPv6 will return all available configuration information.
Type xs:boolean
Used by
Source
 
<xs:attribute name="managed_address_config_flag" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>1-bit "Managed address configuration" flag. When set, it indicates that addresses are available via Dynamic Host Configuration Protocol. If the M flag is set, the O flag is redundant and can be ignored because DHCPv6 will return all available configuration information.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:RouterAdvertisementType / @other_config_flag
Namespace No namespace
Annotations
 
1-bit "Other configuration" flag. When set, it indicates that other configuration information is available via DHCPv6. Examples of such information are DNS-related information or information on other servers within the network.
Type xs:boolean
Used by
Source
 
<xs:attribute name="other_config_flag" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>1-bit "Other configuration" flag. When set, it indicates that other configuration information is available via DHCPv6. Examples of such information are DNS-related information or information on other servers within the network.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:NeighborAdvertisementType / @router_flag
Namespace No namespace
Annotations
 
Router flag. When set, the R-bit indicates that the sender is a router. The R-bit is used by Neighbor Unreachability Detection to detect a router that changes to a host.
Type xs:boolean
Used by
Source
 
<xs:attribute name="router_flag" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>Router flag. When set, the R-bit indicates that the sender is a router. The R-bit is used by Neighbor Unreachability Detection to detect a router that changes to a host.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:NeighborAdvertisementType / @solicited_flag
Namespace No namespace
Annotations
 
Solicited flag. When set, the S-bit indicates that the advertisement was sent in response to a Neighbor Solicitation from the Destination address. The S-bit is used as a reachability confirmation for Neighbor Unreachability Detection.
Type xs:boolean
Used by
Source
 
<xs:attribute name="solicited_flag" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>Solicited flag. When set, the S-bit indicates that the advertisement was sent in response to a Neighbor Solicitation from the Destination address. The S-bit is used as a reachability confirmation for Neighbor Unreachability Detection.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:NeighborAdvertisementType / @override_flag
Namespace No namespace
Annotations
 
Override flag. When set, the O-bit indicates that the advertisement should override an existing cache entry and update the cached link-layer address.
Type xs:boolean
Used by
Source
 
<xs:attribute name="override_flag" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>Override flag. When set, the O-bit indicates that the advertisement should override an existing cache entry and update the cached link-layer address.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:IPVersionType / @datatype
Namespace No namespace
Annotations
 
This attribute is optional and specifies the expected type for the value of the specified property.
Type DatatypeEnum
Used by
Source
 
<xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
  <xs:annotation>
    <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:DoNotFragmentType / @datatype
Namespace No namespace
Annotations
 
This attribute is optional and specifies the expected type for the value of the specified property.
Type DatatypeEnum
Used by
Source
 
<xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
  <xs:annotation>
    <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:MoreFragmentsType / @datatype
Namespace No namespace
Annotations
 
This attribute is optional and specifies the expected type for the value of the specified property.
Type DatatypeEnum
Used by
Source
 
<xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
  <xs:annotation>
    <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:IANAAssignedIPNumbersType / @datatype
Namespace No namespace
Annotations
 
This attribute is optional and specifies the expected type for the value of the specified property.
Type DatatypeEnum
Used by
Source
 
<xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
  <xs:annotation>
    <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:IPv4CopyFlagType / @datatype
Namespace No namespace
Annotations
 
This attribute is optional and specifies the expected type for the value of the specified property.
Type DatatypeEnum
Used by
Source
 
<xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
  <xs:annotation>
    <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:IPv4ClassType / @datatype
Namespace No namespace
Annotations
 
This attribute is optional and specifies the expected type for the value of the specified property.
Type DatatypeEnum
Used by
Source
 
<xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
  <xs:annotation>
    <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:IPv4OptionsType / @datatype
Namespace No namespace
Annotations
 
This attribute is optional and specifies the expected type for the value of the specified property.
Type DatatypeEnum
Used by
Source
 
<xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
  <xs:annotation>
    <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:IPv6DoNotRecogActionType / @datatype
Namespace No namespace
Annotations
 
This attribute is optional and specifies the expected type for the value of the specified property.
Type DatatypeEnum
Used by
Source
 
<xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
  <xs:annotation>
    <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:IPv6PacketChangeType / @datatype
Namespace No namespace
Annotations
 
This attribute is optional and specifies the expected type for the value of the specified property.
Type DatatypeEnum
Used by
Source
 
<xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
  <xs:annotation>
    <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:MFlagType / @datatype
Namespace No namespace
Annotations
 
This attribute is optional and specifies the expected type for the value of the specified property.
Type DatatypeEnum
Used by
Complex Type PacketObj:MFlagType
Source
 
<xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
  <xs:annotation>
    <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:TCPFlagsType / @ns
Namespace No namespace
Annotations
 
ECN-nonce concealment protection.
Type xs:boolean
Used by
Complex Type PacketObj:TCPFlagsType
Source
 
<xs:attribute name="ns" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>ECN-nonce concealment protection.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:TCPFlagsType / @cwr
Namespace No namespace
Annotations
 
Congestion Window Reduced (CWR) flag is set by the sending host to indicate that it received a TCP segment with the ECE flag set and had responded in congestion control mechanism. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
Type xs:boolean
Used by
Complex Type PacketObj:TCPFlagsType
Source
 
<xs:attribute name="cwr" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>Congestion Window Reduced (CWR) flag is set by the sending host to indicate that it received a TCP segment with the ECE flag set and had responded in congestion control mechanism. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:TCPFlagsType / @ece
Namespace No namespace
Annotations
 
ECN-Echo indicates: if the SYN flag is set, that the TCP peer is ECN capable; if the SYN flag is clear, that a packet with Congestion Experienced flag in IP header set is received during normal transmission. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
Type xs:boolean
Used by
Complex Type PacketObj:TCPFlagsType
Source
 
<xs:attribute name="ece" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>ECN-Echo indicates: if the SYN flag is set, that the TCP peer is ECN capable; if the SYN flag is clear, that a packet with Congestion Experienced flag in IP header set is received during normal transmission. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:TCPFlagsType / @urg
Namespace No namespace
Annotations
 
Indicates that the Urgent point field is significant.
Type xs:boolean
Used by
Complex Type PacketObj:TCPFlagsType
Source
 
<xs:attribute name="urg" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>Indicates that the Urgent point field is significant.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:TCPFlagsType / @ack
Namespace No namespace
Annotations
 
indicates that the Acknowledgment field is significant. All packets after the initial SYN packet sent by the client should have this flag set. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
Type xs:boolean
Used by
Complex Type PacketObj:TCPFlagsType
Source
 
<xs:attribute name="ack" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>indicates that the Acknowledgment field is significant. All packets after the initial SYN packet sent by the client should have this flag set. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:TCPFlagsType / @psh
Namespace No namespace
Annotations
 
Push functions. asks to push the buffered dtata to the receiving application. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
Type xs:boolean
Used by
Complex Type PacketObj:TCPFlagsType
Source
 
<xs:attribute name="psh" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>Push functions. asks to push the buffered dtata to the receiving application. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:TCPFlagsType / @rst
Namespace No namespace
Annotations
 
Reset the connection.
Type xs:boolean
Used by
Complex Type PacketObj:TCPFlagsType
Source
 
<xs:attribute name="rst" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>Reset the connection.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:TCPFlagsType / @syn
Namespace No namespace
Annotations
 
Synchronize sequence numbers. Only the first packet sent from each end should have this flag set. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
Type xs:boolean
Used by
Complex Type PacketObj:TCPFlagsType
Source
 
<xs:attribute name="syn" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>Synchronize sequence numbers. Only the first packet sent from each end should have this flag set. http://en.wikipedia.org/wiki/Transmission_Control_Protocol.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:TCPFlagsType / @fin
Namespace No namespace
Annotations
 
If this flag is set, it means there is no more data from sender.
Type xs:boolean
Used by
Complex Type PacketObj:TCPFlagsType
Source
 
<xs:attribute name="fin" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>If this flag is set, it means there is no more data from sender.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PacketObj:IANAPortNumberRegistryType / @datatype
Namespace No namespace
Annotations
 
This attribute is optional and specifies the expected type for the value of the specified property.
Type DatatypeEnum
Used by
Source
 
<xs:attribute name="datatype" type="cyboxCommon:DatatypeEnum" fixed="string">
  <xs:annotation>
    <xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
  </xs:annotation>
</xs:attribute>
XML Schema documentation generated by ® XML Editor.