On Mar 11, 2015, at 8:54 PM, Russ Housley hous...@vigilsec.com wrote:
About two years ago, I was at a workshop where someone claimed that the
Vendor Identifiers that are exchanged in IKE are very useful for dealing with
bugs. The claim was that following the report of a bug, others could
In our work we have not encountered any situations where the Vendor
Identification was relevant.
paul
On Mar 11, 2015, at 2:54 PM, Russ Housley hous...@vigilsec.com wrote:
About two years ago, I was at a workshop where someone claimed that the
Vendor Identifiers that are exchanged
About two years ago, I was at a workshop where someone claimed that the Vendor
Identifiers that are exchanged in IKE are very useful for dealing with bugs.
The claim was that following the report of a bug, others could adjust their
behaviors to avoid the circumstances that enable the bug. In
On Wed, 11 Mar 2015, Russ Housley wrote:
About two years ago, I was at a workshop where someone claimed that the Vendor
Identifiers that are exchanged in IKE are very useful for dealing with bugs.
The claim was that following the report of a bug, others could adjust their
behaviors to avoid
On Mar 12, 2015, at 1:38 AM, paul_kon...@dell.com wrote:
On Mar 11, 2015, at 5:23 PM, Yoav Nir ynir.i...@gmail.com wrote:
On Mar 11, 2015, at 8:54 PM, Russ Housley hous...@vigilsec.com wrote:
About two years ago, I was at a workshop where someone claimed that the
Vendor
On Mar 11, 2015, at 5:23 PM, Yoav Nir ynir.i...@gmail.com wrote:
On Mar 11, 2015, at 8:54 PM, Russ Housley hous...@vigilsec.com wrote:
About two years ago, I was at a workshop where someone claimed that the
Vendor Identifiers that are exchanged in IKE are very useful for dealing
with
On 3/11/15, 11:38 PM, paul_kon...@dell.com paul_kon...@dell.com wrote:
As for buggy implementations, I think that it isn’t needed for that. If
someone has a bug that breaks interoperability, we would in general take
the view of “if they fix it, it will work” — in other words, vendors