Skip to content

Commit

Permalink
Merge pull request #1074 from ietf-tapswg/csperkins-1072
Browse files Browse the repository at this point in the history
Clarify use of API calls for multicast
  • Loading branch information
tfpauly authored Sep 26, 2022
2 parents 5ffd650 + ba2a196 commit 9e39104
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion draft-ietf-taps-interface.md
Original file line number Diff line number Diff line change
Expand Up @@ -764,13 +764,14 @@ with the Local Endpoint set to the group address. The set of Connection
objects created forms a Connection Group.
The receiving interface can be restricted by passing it as part of the LocalSpecifier or queried through the MessagContext on the messages received (see {{msg-ctx}} for further details).

The following API calls can be used to configure a Preconnection before calling Listen():

~~~
LocalSpecifier.WithSingleSourceMulticastGroupIPv4(GroupAddress, SourceAddress)
LocalSpecifier.WithSingleSourceMulticastGroupIPv6(GroupAddress, SourceAddress)
LocalSpecifier.WithAnySourceMulticastGroupIPv4(GroupAddress)
LocalSpecifier.WithAnySourceMulticastGroupIPv6(GroupAddress)
LocalSpecifier.WithPort(PortNumber)
LocalSpecifier.WithTTL(TTL)
~~~

Calling Rendezvous() on a Preconnection with an any-source multicast group
Expand All @@ -784,6 +785,8 @@ Endpoint.
Calling Rendezvous() on a Preconnection with a source-specific multicast
group address as the Local Endpoint results in an EstablishmentError.

The following API calls can be used to configure a Preconnection before calling Rendezvous():

~~~
RemoteSpecifier.WithMulticastGroupIPv4(GroupAddress)
RemoteSpecifier.WithMulticastGroupIPv6(GroupAddress)
Expand Down

0 comments on commit 9e39104

Please sign in to comment.