[dhcwg] Re: New Version Notification for draft-ietf-dhc-dhcp v4-over-dhcpv6-ra-00.txt

Hi Med,

thanks for the review!

Just on the github. Apparently, there was a wrong name in the doc. This is the right link:

https://github.com/mirjak/draft-dhc-dhcpv4-over-dhcpv6-ra

Mirja



On 31.01.25, 16:37, "[email protected] <mailto:[email protected]>" <[email protected] <mailto:[email protected]>> wrote:


Hi Claudio,


Thank you for taking care of the comments raised in my review.


This version looks better. There is one pending item that I think is worth to cover in the text: the relay does not have to mirror this part of rfc7341:


" the client can
configure the address and other relevant parameters on this
interface."


As I was reviewing the diff, I tagged these nits:


OLD: there's a DHCPv6 server than can provide IPv4
NEW: there's a DHCPv6 server that can provide IPv4


OLD: In this document when not otherwise specified it referres
NEW: In this document, when not otherwise specified, refers


OLD: because for IPv4 it is only the first Relay Agent that can
NEW: because for IPv4 only the first Relay Agent can


OLD: where the whole The Relay Agent
NEW: where the Relay Agent


BTW, I still get a 404 when accessing https://github.com/mirjak/dhc-dhcpv4-over-dhcpv6-ra <https://github.com/mirjak/dhc-dhcpv4-over-dhcpv6-ra>


Cheers,
Med


> -----Message d'origine-----
> De : Claudio Porfiri
> <[email protected] <mailto:[email protected]>>
> Envoyé : mardi 7 janvier 2025 09:35
> À : Jari Arkko <[email protected] <mailto:[email protected]>>; Mirja Kuehlewind
> <[email protected] <mailto:[email protected]>>; Suresh Krishnan
> <[email protected] <mailto:[email protected]>>; [email protected] <mailto:[email protected]>
> Objet : [dhcwg] FW: New Version Notification for draft-ietf-dhc-
> dhcpv4-over-dhcpv6-ra-00.txt
>
>
> Hi,
> Sorry for the late comment.
> The new version of the document has included the changes
> suggested by the reviewers, mainly by the addition of
> clarifications.
> We have added the applicability section, refined the relationship
> with RFC7341, explained the role of the first RA versus the
> following and enhanced the security considerations.
> When related to the Radio Fronthaul Network Use Case in the
> appendix, the description was enhanced by generalization.
> As commented, there are no changes in IANA and nothing prevents
> an implementation.
>
> Thanks and best regards,
> Claudio (from the author's team).
>
> -----Original Message-----
> From: [email protected] <mailto:[email protected]> <[email protected] <mailto:[email protected]>>
> Sent: Tuesday, December 17, 2024 11:30 AM
> To: Mirja Kühlewind <[email protected] <mailto:[email protected]>>; Claudio
> Porfiri <[email protected] <mailto:[email protected]>>; Jari Arkko
> <[email protected] <mailto:[email protected]>>; Mirja Kuehlewind
> <[email protected] <mailto:[email protected]>>; Suresh Krishnan
> <[email protected] <mailto:[email protected]>>
> Subject: New Version Notification for draft-ietf-dhc-dhcpv4-over-
> dhcpv6-ra-00.txt
>
> A new version of Internet-Draft draft-ietf-dhc-dhcpv4-over-
> dhcpv6-ra-00.txt
> has been successfully submitted by Mirja Kühlewind and posted to
> the IETF repository.
>
> Name: draft-ietf-dhc-dhcpv4-over-dhcpv6-ra
> Revision: 00
> Title: DHCPv4 over DHCPv6 with Relay Agent Support
> Date: 2024-12-17
> Group: dhc
> Pages: 10
> URL:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%252 <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%252>
> Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-dhc-dhcpv4-over-dhcpv6-
> ra-
> 00.txt&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cbc7497b1cc
> e44e36ccd508dd2ef64f8f%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0
> %7C638718357607095023%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR
> ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy
> fQ%3D%3D%7C0%7C%7C%7C&sdata=GoDp8Y3dF1Iy4tMNHciwP752YfznDPVHxLgl2
> GDWPys%3D&reserved=0
> Status:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%252 <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%252>
> Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-dhc-dhcpv4-over-dhcpv6-
> ra%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cbc7497b1cce
> 44e36ccd508dd2ef64f8f%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%
> 7C638718357607113315%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRy
> dWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf
> Q%3D%3D%7C0%7C%7C%7C&sdata=cUVEshx1FoEiNy%2FfxhiLPI7WzKJntRyOyht%
> 2FZqCoZ7E%3D&reserved=0
> HTML:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%252 <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%252>
> Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-dhc-dhcpv4-over-dhcpv6-
> ra-
> 00.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cbc7497b1c
> ce44e36ccd508dd2ef64f8f%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C
> 0%7C638718357607122298%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn
> RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjo
> yfQ%3D%3D%7C0%7C%7C%7C&sdata=mTSLw510orvLVIxy9nBt1PIoOLGMARrGS9gH
> SboY2Lk%3D&reserved=0
> HTMLized:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%252 <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%252>
> Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-dhc-dhcpv4-over-
> dhcpv6-
> ra&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cbc7497b1cce44e
> 36ccd508dd2ef64f8f%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6
> 38718357607130960%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWU
> sIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3
> D%3D%7C0%7C%7C%7C&sdata=XBpAwSVtg%2Ba5OqUvlzNyW878Xz%2FisxkMB0ZmL
> RS8sVY%3D&reserved=0
>
>
> Abstract:
>
> This document describes a mechanism for networks with legacy
> IPv4-only clients to use services provided by DHCPv6 using
> DHCPv4-
> over-DHCPv6 (DHCP 4o6) in a Relay Agent. RFC7341 specifies
> use of
> DHCPv4-over-DHCPv6 in the client only. This document
> specifies a
> RFC7341-based approach that allows DHCP 4o6 to be deployed as
> a Relay
> Agent (4o6RA) that implements the 4o6 DHCP en- and
> decapsulation if
> this is not possible at the client.
>
>
>
> The IETF Secretariat
>
>
> _______________________________________________
> dhcwg mailing list -- [email protected] <mailto:[email protected]>
> To unsubscribe send an email to [email protected] <mailto:[email protected]>
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.


This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.





_______________________________________________
dhcwg mailing list -- [email protected]
To unsubscribe send an email to [email protected]