If there is previous art using this naming then all good for me. It was odd naming to read. When I read “dummy” earlier today, I associated this word with “little bit stupid”. That negative connotation sounded slightly unnecessary, and hence my observation. If this naming is already widespread used with other technologies, then we could name these dummy addresses.
G/ From: Eric Vyncke (evyncke) <evyn...@cisco.com> Sent: Tuesday, February 18, 2025 9:41 PM To: Greg Mirsky <gregimir...@gmail.com>; Gunter van de Velde (Nokia) <gunter.van_de_ve...@nokia.com>; James Guichard <james.n.guich...@futurewei.com> Cc: nvo3@ietf.org; draft-ietf-nvo3-geneve-...@ietf.org Subject: Re: [nvo3] I-D Action: draft-ietf-nvo3-geneve-oam-15.txt CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information. Gunter, The choice of “Dummy” is a reference to the “Dummy IPv4 Address” specified by 4RD -éric From: Greg Mirsky <gregimir...@gmail.com<mailto:gregimir...@gmail.com>> Date: Tuesday, 18 February 2025 at 15:36 To: Gunter van de Velde (Nokia) <gunter.van_de_ve...@nokia.com<mailto:gunter.van_de_ve...@nokia.com>>, Eric Vyncke (evyncke) <evyn...@cisco.com<mailto:evyn...@cisco.com>>, James Guichard <james.n.guich...@futurewei.com<mailto:james.n.guich...@futurewei.com>> Cc: nvo3@ietf.org<mailto:nvo3@ietf.org> <nvo3@ietf.org<mailto:nvo3@ietf.org>>, draft-ietf-nvo3-geneve-...@ietf.org<mailto:draft-ietf-nvo3-geneve-...@ietf.org> <draft-ietf-nvo3-geneve-...@ietf.org<mailto:draft-ietf-nvo3-geneve-...@ietf.org>> Subject: Re: [nvo3] I-D Action: draft-ietf-nvo3-geneve-oam-15.txt Hi Gunter, thank you for raising this question. The IPv6 Dummy prefix is introduced to address Eric's concern about the use of the IPv6 loopback address as the IP destination address in the encapsulated IP/UDP active OAM packet. I am working on updating draft-ietf-mpls-p2mp-bfd<https://datatracker.ietf.org/doc/draft-ietf-mpls-p2mp-bfd/> to address Eric's COMMENTS. I'll be glad to use any other name for the new IPv6 prefix that the draft requests to be added in IPv6 Special-Purpose Address Registry. I greatly appreciate your guidance, advice. Regards, Greg On Tue, Feb 18, 2025 at 12:52 AM Gunter van de Velde (Nokia) <gunter.van_de_ve...@nokia.com<mailto:gunter.van_de_ve...@nokia.com>> wrote: Hi Greg, Thanks for the update. I was scanning through the updated draft. I see that that a fresh IPv6 range is now introduced using the name " Dummy IPv6 range TBA2/64". Maybe the term "dummy" might not be ideal as it can sound informal or imprecise. Is there another name that you think could be used? For example placeholder, stub address or virtual loop or so? Any thoughts about this? G/ -----Original Message----- From: internet-dra...@ietf.org<mailto:internet-dra...@ietf.org> <internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>> Sent: Tuesday, February 18, 2025 12:36 AM To: i-d-annou...@ietf.org<mailto:i-d-annou...@ietf.org> Cc: nvo3@ietf.org<mailto:nvo3@ietf.org> Subject: [nvo3] I-D Action: draft-ietf-nvo3-geneve-oam-15.txt CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext<http://nok.it/ext> for additional information. Internet-Draft draft-ietf-nvo3-geneve-oam-15.txt is now available. It is a work item of the Network Virtualization Overlays (NVO3) WG of the IETF. Title: Active OAM for use in Geneve Authors: Greg Mirsky Sami Boutros David Black Santosh Pallagatti Name: draft-ietf-nvo3-geneve-oam-15.txt Pages: 11 Dates: 2025-02-17 Abstract: Geneve (Generic Network Virtualization Encapsulation) is a flexible and extensible network virtualization overlay protocol designed to encapsulate network packets for transport across underlying physical networks. This document specifies the requirements and provides a framework for Operations, Administration, and Maintenance (OAM) in Geneve networks. It outlines the OAM functions necessary to monitor, diagnose, and troubleshoot Geneve overlay networks to ensure proper operation and performance. The document aims to guide the implementation of OAM mechanisms within the Geneve protocol to support network operators in maintaining reliable and efficient virtualized network environments. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-nvo3-geneve-oam/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-nvo3-geneve-oam-15.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-nvo3-geneve-oam-15 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ nvo3 mailing list -- nvo3@ietf.org<mailto:nvo3@ietf.org> To unsubscribe send an email to nvo3-le...@ietf.org<mailto:nvo3-le...@ietf.org>
_______________________________________________ nvo3 mailing list -- nvo3@ietf.org To unsubscribe send an email to nvo3-le...@ietf.org
