[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
MACsec SFP
On (2014-06-30 13:28 +0930), Glen Turner wrote:
> After the SFF Committee specifies the registers the operating system vendors or vendors of devices would then add commands to support to toggle the I2C needed to program those registers with MACsec keys, etc.
This is what I tried to tackle, this creates chicken/egg scenario, no one is
buying optic, because you can't program it from your router, and you can't
program it in your router, as no one is using the optic and vendor won't put
development hours on it.
If instead there would be standardized (DHCP option like) system to code
arbitrary value to arbitrary location, you could code the feature, without
router understanding what it is, after a while, syntactic sugar might be added
for convenience.
--
++ytti
- References:
- MACsec SFP
- From: saku at ytti.fi (Saku Ytti)
- MACsec SFP
- From: phulshof at aimvalley.nl (Pieter Hulshoff)
- MACsec SFP
- From: morrowc.lists at gmail.com (Christopher Morrow)
- MACsec SFP
- From: phulshof at aimvalley.nl (Pieter Hulshoff)
- MACsec SFP
- From: morrowc.lists at gmail.com (Christopher Morrow)
- MACsec SFP
- From: phulshof at aimvalley.nl (Pieter Hulshoff)
- MACsec SFP
- From: jschiel at flowtools.net (John Schiel)
- MACsec SFP
- From: phulshof at aimvalley.nl (Pieter Hulshoff)
- MACsec SFP
- From: saku at ytti.fi (Saku Ytti)
- MACsec SFP
- From: gdt at gdt.id.au (Glen Turner)