proposal: net: add the "Description" field for interfaces on Windows hosts

[eoinmiller]

This proposal modifies Go to add the "Description" field for interfaces on Windows hosts.

The "Description" field, rather than "FriendlyName", is used by Windows Performance Monitor and others when identifying interfaces. Making both fields accessible makes correlating back to specific interfaces easier. New to this, apologies if I am not following along to the process very well!

Reference - IP_ADAPTER_ADDRESSES_LH structure (iptypes.h):
https://learn.microsoft.com/en-us/windows/win32/api/iptypes/ns-iptypes-ip_adapter_addresses_lh

For #61033

[ianlancetaylor]

What are examples of the contents of both fields on a Windows system? Thanks.

[ianlancetaylor]

CC @golang/windows

[eoinmiller]

Example values:

Name         : Ethernet0
Description  : Intel(R) 82574L Gigabit Network Connection

Name         : Loopback Pseudo-Interface 1
Description  : Software Loopback Interface 1

Description field is shown via tools such as ipconfig as well:

>ipconfig /all
...
Ethernet adapter Ethernet0:
...
   Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
...

When attempting to attribute interface information back to other sources, such as windows performance monitors, the names are closer to "Description" (Description) rather than "Name" (FriendlyName).

[alexbrainman]

@eoinmiller

We already have "Interface.Name". Adding "Interface.Description" would just add confusion between the two.

What is the problem that you are trying to solve? Thank you.

Also adding @bradfitz because he is an expert in Windows networking.

Alex