Subject: [dhcwg] Authentication in draft-donley-dhc-cer-id-option?

From: Ted Lemon <[email-masked]>
Date: Sun, 2 Mar 2014 15:27:37 +0000

Why does the CER-id option have its own authentication?   There is already an authentication mechanism in RFC3315 that does what your current authentication option does, and there is work being presented at this IETF on how to do public-key authentication as well.   Adding extra keying seems bad, unless the point is to carry that keying downstream from the CER to devices that do not share a link with the CER.   Even so, it's not clear to me that there's any value in this.

It would be helpful to discuss the security model in the introduction.