[ Moderators note: Post was moderated, either because it was posted by
a non-subscriber, or because it was over 20K.
With the massive amount of spam, it is easy to miss and therefore
delete relevant posts by non-subscribers.
Please fix your subscription addresses. ]


No, this would just mean that the client identity would be stored in raw
octet form instead of "encrypting" the data. It would have no impact on
anything else that I can see.

- Bernie

> -----Original Message-----
> From: Harald Tveit Alvestrand [mailto:harald@alvestrand.no]=20
> Sent: Tuesday, February 07, 2006 5:36 PM
> To: Bernie Volz (volz); Ted Lemon; dhcwg@ietf.org
> Cc: namedroppers@ops.ietf.org; Olaf Kolkman; Stig Venaas;=20
> ogud@ogud.com; Ralph Droms (rdroms)
> Subject: RE: [dhcwg] Open issues in DHCP FQDN, DHCID and=20
> DDNS-DHCP Related RFCs
> --On tirsdag, februar 07, 2006 17:28:54 -0500 "Bernie Volz (volz)"=20
> wrote:
> > Well, that certainly would be an easy solution (in terms of=20

> changes to
> > the draft and also the conflict resolution draft). But, do=20

> how practical
> > is this? How likely is the IESG to accept this?

> (speaking as DHCP-head, not security-head)
> would removing the hash entirely increase the probability of=20
> confusion over=20
> "who does what"?
> I thought it had a differentiation function too....
> Harald

to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.