From: Zbigniew Jędrzejewski-Szmek Date: Tue, 29 Sep 2020 10:27:19 +0000 (+0200) Subject: man/systemd.network(5): unify descriptions of MUDURL= X-Git-Tag: v247-rc1~145^2~1 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=0558f3035fac84f008cb7ddf215887c3087decb1;p=thirdparty%2Fsystemd.git man/systemd.network(5): unify descriptions of MUDURL= Let's write one good description and refer to it from the other two spots. --- diff --git a/man/systemd.network.xml b/man/systemd.network.xml index 02d56480b53..dc295198c37 100644 --- a/man/systemd.network.xml +++ b/man/systemd.network.xml @@ -1548,11 +1548,16 @@ IPv6Token=prefixstable:2002:da8:1:: MUDURL= - When configured, the Manufacturer Usage Descriptions (MUD) URL will be sent to the - DHCPv4 server. Takes an URL of length up to 255 characters. A superficial verification that - the string is a valid URL will be performed. DHCPv4 clients are intended to have at most one - MUD URL associated with them. See - RFC 8520. + When configured, the specified Manufacturer Usage Description (MUD) URL will be sent to the + DHCPv4 server. Takes a URL of length up to 255 characters. A superficial verification that the + string is a valid URL will be performed. DHCPv4 clients are intended to have at most one MUD URL + associated with them. See RFC 8520. + + + MUD is an embedded software standard defined by the IETF that allows IoT device makers to + advertise device specifications, including the intended communication patterns for their device + when it connects to the network. The network can then use this to author a context-specific + access policy, so the device functions only within those parameters. @@ -1847,10 +1852,9 @@ IPv6Token=prefixstable:2002:da8:1:: MUDURL= - When configured, the Manufacturer Usage Descriptions (MUD) URL will be sent to the DHCPV6 server. - Takes an URL of length up to 255 characters. A superficial verification that the string is a valid URL - will be performed. DHCPv6 clients are intended to have at most one MUD URL associated with them. See - RFC 8520. + When configured, the specified Manufacturer Usage Description (MUD) URL will be sent to + the DHCPV6 server. The syntax and semantics are the same as for MUDURL= in the + [DHCPv4] section described above. @@ -2567,14 +2571,11 @@ IPv6Token=prefixstable:2002:da8:1:: MUDURL= - Controls support for Ethernet LLDP packet's Manufacturer Usage Description (MUD). MUD is an embedded software - standard defined by the IETF that allows IoT Device makers to advertise device specifications, including the intended - communication patterns for their device when it connects to the network. The network can then use this intent to author - a context-specific access policy, so the device functions only within those parameters. Takes an URL of length up to 255 - characters. A superficial verification that the string is a valid URL - will be performed. See - RFC 8520 for details. The MUD URL received - from the LLDP packets will be saved at the state files and can be read via + When configured, the specified Manufacturer Usage Descriptions (MUD) URL will be sent in + LLDP packets. The syntax and semantics are the same as for MUDURL= in the + [DHCPv4] section described above. + + The MUD URLs received via LLDP packets are saved and can be read using the sd_lldp_neighbor_get_mud_url() function.