{"push_id":2634352583,"size":1,"distinct_size":1,"ref":"refs/heads/duid","head":"7fad37e70e9b84c6e4ddc370367d4ea9d4e03d3e","before":"1d814306f252a243bf977da390b4b2b2854c1a66","commits":[{"sha":"7fad37e70e9b84c6e4ddc370367d4ea9d4e03d3e","author":{"name":"Michael Stapelberg","email":"97e0203ad32d728c266b6422d4bd97c18b9b600f@google.com"},"message":"Pass through unknown DUIDs\n\nI’m building on a program which works with user-supplied DUIDs. Before this\nchange, the code would panic when users provide a DUID which is not (yet)\nimplemented.\n\nIn addition to this being a better failure mode, the behavior is also mandated\nby the DHCPv6 RFC: https://tools.ietf.org/html/rfc3315#section-9 states:\n\n    Clients and servers MUST treat DUIDs as opaque values and MUST only\n    compare DUIDs for equality.","distinct":true,"url":"https://api.github.com/repos/stapelberg/dhcp/commits/7fad37e70e9b84c6e4ddc370367d4ea9d4e03d3e"}]}
{"actor":{"display_login":"stapelberg"}}