Extracting solicitor's relayed peer-address, using EUI-64 for lease IID.
"Paul Duffy (paduffy)" <[email protected]> Thu, 14 Dec 2023 19:14:03 +0000
| Newsgroups | gmane.network.dhcp.isc.dhcp-server |
|---|---|
| Message-ID | <MN2PR11MB37576F8F5FFADA484A80F8CFB98CA@MN2PR11MB3757.namprd11.prod.outlook.com> |
--===============1826455270477625454==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_MN2PR11MB37576F8F5FFADA484A80F8CFB98CAMN2PR11MB3757namp_"
--_000_MN2PR11MB37576F8F5FFADA484A80F8CFB98CAMN2PR11MB3757namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Greetings from a very large IPv6 IoT deployment which is using DHCPv6 for a=
ddress assignments.
The technology requires field devices form their link-local IPv6 address wi=
th interface identifier being the modified EUI-64 format described in RFC 4=
291. The solicitor's link-local IPv6 address will be contained in the peer=
-address field relayed to the DHCPv6 service.
Is ISC able to extract the EUI-64 from the peer-address link-local and use =
that as the IID for an address lease to the soliciting device?
Thanks in advance.
--_000_MN2PR11MB37576F8F5FFADA484A80F8CFB98CAMN2PR11MB3757namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72" style=3D"word-wrap:=
break-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Greetings from a very large IPv6 IoT deployment whic=
h is using DHCPv6 for address assignments.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">The technology requires field devices form their lin=
k-local IPv6 address with interface identifier being the modified EUI-64 fo=
rmat described in RFC 4291. The solicitor’s link-local IPv6 add=
ress will be contained in the peer-address field
relayed to the DHCPv6 service.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Is ISC able to extract the EUI-64 from the peer-addr=
ess link-local and use that as the IID for an address lease to the soliciti=
ng device?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Thanks in advance.<o:p></o:p></p>
</div>
</body>
</html>
--_000_MN2PR11MB37576F8F5FFADA484A80F8CFB98CAMN2PR11MB3757namp_--
--===============1826455270477625454==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users
--===============1826455270477625454==--