From 2d324bd6120dc05e26edbc179292caa795821ff9 Mon Sep 17 00:00:00 2001 From: crimson Date: Tue, 10 Oct 2023 13:47:35 +0200 Subject: [PATCH] fix-lint --- draft-ietf-core-groupcomm-bis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-core-groupcomm-bis.md b/draft-ietf-core-groupcomm-bis.md index 216eb54..09b29a6 100644 --- a/draft-ietf-core-groupcomm-bis.md +++ b/draft-ietf-core-groupcomm-bis.md @@ -290,7 +290,7 @@ Different types of groups are named as specified below, separately for CoAP grou A CoAP group is always defined by the two properties of IP multicast address and UDP port number (see {{sec-groupdef-coapgroup}}). However, a CoAP group is for practical purposes identified and named by the authority component in the group URI. This component includes the host subcomponent and an optional UDP port number. -The host subcomponent directly defines the IP multicast address of the CoAP group, in case the host consists of an IP literal. +The host subcomponent directly defines the IP multicast address of the CoAP group, in case the host consists of an IP literal. The host subcomponent indirectly defines the IP multicast address of the CoAP group, in case the host consists of a hostname: resolving the hostname to an IP address in this case produces the IP multicast address. It follows that the same CoAP group might have multiple names, which can be simultaneously and interchangeably used. For example, if the two hostnames group1.com and group1.alias.com both resolve to the IP multicast address \[ff15::1234\], then the following authority components are all names for the same CoAP group.