On 1/8/14, 3:32 AM, Stephen Farrell wrote: > > > On 01/08/2014 06:59 AM, Eliot Lear wrote: >> >> On 1/8/14 7:52 AM, Stefan Winter wrote: >> >>> In short: MAC addresses are NOT necessarily local to the LAN; if they >>> leak beyond, privacy is at risk. The LAN may be IEEE's domain; protocols >>> that transport information about MAC addresses on the layers above are >>> most certainly IETF work. >>> >>> >> >> Indeed. Mac addresses are also found in location registrations for some >> services. > > And even, horribly, in the DNS [1] - which is one of > those "better to document than ignore" things.
In both cases the scope in which their appropriate to use is germaine. If you do layer-2 authentication or resource allocation it would seems likely that you would collect and store layer-2 identifiers for future use. DHCP servers do this also. Should this information (L2 binding to some upper layer information) be exposed to applications that don't need the L2 binding? I don't think so. > S. > > [1] http://tools.ietf.org/html/rfc7043 > >> >> Eliot >> _______________________________________________ >> perpass mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/perpass >> >> > _______________________________________________ > perpass mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/perpass >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ perpass mailing list [email protected] https://www.ietf.org/mailman/listinfo/perpass
