On 04/29/2016 11:50 AM, Hefty, Sean wrote:
>> This doesn't seem to make any sense to me. Without going back and
>> re-reading this part of the spec, as I recall, there is:
>>
>> UnJoined
>> SendOnly Join
>> Full Join
>
> The 1.2.1 version of the spec has:
>
> JoinState - 4 bits
>
> Join/Leave Status requested by the port. See discussion below.
> bit 0: FullMember: Include/delete this endport from the multicast group as a
> member sender and receiver.
> bit 1: NonMember: Include/delete this endport from the multicast group as
> a non-member sender and receiver.
> bit 2: SendOnlyNonMember: Include/delete this endport from the multicast
> group as a non-member sender only.
> bit 3: Reserved
>
> • FullMember: Group messages are routed both to and from the port.
> The port is considered a member for purposes of group creation and
> deletion, i.e.: if no member ports with FullMember=1 remain, the
> group may be deleted; otherwise it may not.
> • NonMember: Group messages are routed both to and from the port.
> The port is not considered a member for purposes of group creation/deletion.
> • SendOnlyNonMember: Group messages are only routed from the
> port; none are routed to the port. The port is not considered
> a member for purposes of group creation/deletion.
>
> Any combination of the MCMemberRecord:JoinState bits may be 1. When
> multiple bits are 1, the qualities of the port's type of membership are the
> union of the qualities specified by the bits that are 1.
>
OK, that makes more sense. Thanks for the refresher.
--
Doug Ledford <dledford@xxxxxxxxxx>
GPG KeyID: 0E572FDD
Attachment:
signature.asc
Description: OpenPGP digital signature
