<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:595.3pt 841.9pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=FR link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Hi,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'>Actually, the changes I
brought to the DHCP source code don’t force DHCPv4 clients to use DUID
based client-identifiers in order to keep backward compatibility. Forcing every
user to migrate to this new kind of client-identifiers would be a mess. That’s
why I’ve chosen to enable the use of a DUID based client-identifier only
if the required argument is passed to the dhclient executable. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'>Regarding the DHCID, I
intended to add a new compilation option (I’ve already started to implement
it) that would enable the support of real DHCID records. This option would be
by default disabled: in this case, the old TXT records would be used. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'>Guys, what do you think
about this? <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'>Thomas.<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-GB
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>De :</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
dhcp-workers-bounces+thomas.pegeot=sogeti.com@lists.isc.org
[mailto:dhcp-workers-bounces+thomas.pegeot=sogeti.com@lists.isc.org] <b><span
style='font-weight:bold'>De la part de</span></b> Rene Garcia<br>
<b><span style='font-weight:bold'>Envoyé :</span></b> lundi 15 mars 2010
16:26<br>
<b><span style='font-weight:bold'>À :</span></b>
dhcp-workers@lists.isc.org<br>
<b><span style='font-weight:bold'>Objet :</span></b> Re: On-going work on
DHCP project : RFC4361 support</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>Hi,<o:p></o:p></span></font></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>Here is
some additional information on Thomas'work : the stored DHCID in DNS
servers will change and therefore upgrading to this new behaviour will need a
lot of work to migrate old emulated TXT DHCID to new ones. That's why I aked
him to add support for real DHCID RRs in DNS as ISC BIND 9.5+ seems to handle
them.<o:p></o:p></span></font></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>Including
Thomas'code change into the CVS tree is a major change and creates an
incompatibility with existing DNS records. How can we handle this ? Maybe using
an optional compilation using a new --enable-feature option in configure script
?<o:p></o:p></span></font></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>Therefore
I hope his work will be usefull for the DHCP project.<o:p></o:p></span></font></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>Regards,<br>
René GARCIA<o:p></o:p></span></font></p>
<p style='margin-bottom:12.0pt'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>Quoting Thomas PEGEOT
<thomas.pegeot@sogeti.com>:<br>
<br>
> Hello,<br>
><br>
><br>
><br>
> As part of my final year project (French equivalent of a Master degree in<br>
> computing science), I’m working on an ipv4 to ipv6 migration
research<br>
> project.<br>
><br>
><br>
><br>
> First, I was asked to work on ISC DHCP in order to make dual stack clients<br>
> be able to identity correctly for DDNS updates. This consists in solving
the<br>
> problem described in the “Dual IPv4/IPv6 Client
Considerations” part of the<br>
> RFC 4703 and therefore implementing the RFC 4361. It aims at allowing
DHCPv4<br>
> clients to be identified by an IAID and a DUID, and in that way having<br>
> DHCPv4 and DHCPv6 clients compute the same DHCID from a common DUID.<br>
><br>
><br>
><br>
> The modifications I wrote are currently reviewed by my tutor (René Garcia,<br>
> who already reported bugs here). Afterwards, I’m going to send these
patches<br>
> to this mailing list in hopes of having them merged with the CVS code.<br>
><br>
><br>
><br>
> As the DHCID support is not implemented yet in ISC DHCP, I’m going
now to<br>
> study this problem and try to write down patches in order to solve this. I<br>
> will keep you informed about this.<br>
><br>
><br>
><br>
> I hope that you will be interested in my work.<br>
><br>
><br>
><br>
> Regards,<br>
><br>
><br>
><br>
> Thomas PEGEOT<br>
><br>
><o:p></o:p></span></font></p>
</div>
</body>
</html>