[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti-cybox] IPv4 and IPv6 Address Objects
Yes, this will be an issue in places where multiple types of objects are supported as references. However, going to a single “IP Address” type won’t fix it, as you’ll still have to specify
an “address_type” or similar field to differentiate between IPv4/IPv6. Also, as Jeff and others have mentioned, the primary reason for having separate Objects is that this leads to clearer semantics in the data model. There are places where we want to restrict
addresses to specific types, and therefore having separate IPv4/IPv6 address types was the consensus solution that we came up with. Let’s not rehash this debate. Regards, Ivan From:
<cti-cybox@lists.oasis-open.org> on behalf of Jason Keirstead <Jason.Keirstead@ca.ibm.com> I apologize for my confusing example where I changed from MAC address to IP address half way through my email.. I have not yet had enough coffee... network-connection-object:src_ref.value = '1.2.3.4'
network-connection-object:src_ref.type = 'ipv4-address-object' AND network-connection-object:src_ref.value = '1.2.3.4'
network-connection-object:src_ref.value = '42:29:82:8d:b5:a9'
network-connection-object:src_ref.type = 'ipv4-address-object' AND network-connection-object:src_ref.value = '1.2.3.4'
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]