-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for creating/modifying IPMC group with member list. #2121
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
### IP Multicast Group with members | ||
|
||
Allow IP Multicast Group to be created/modified by specifying the list of members | ||
|
||
### Motivation | ||
|
||
The existing IPMC workflow | ||
* Create a IPMC group | ||
* Add/remove members to this group | ||
|
||
We describe a sample workflow | ||
* A is added to the group | ||
* B is added to the group | ||
* The path to A goes down, so an alternate member A' is added | ||
* Subsequently the primary path to A is restored, so A' needs to be swapped with A | ||
|
||
We have two ways to acheive this. | ||
* remove A' and then add A leading to a small window where no traffic is received by the receiver. | ||
* add A and then remove A' leading to a small window wheret duplicate traffic is received. | ||
|
||
We'd like to avoid both of these scenarios. | ||
|
||
### Proposal | ||
|
||
Specify the full current list of multicast group members at create and update time. | ||
|
||
* Introduce an attribute specifying that the IPMC group members are specified upfront. | ||
* Add a IPMC group attribute for the list of members | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -60,6 +60,26 @@ typedef enum _sai_ipmc_group_attr_t | |
*/ | ||
SAI_IPMC_GROUP_ATTR_IPMC_MEMBER_LIST, | ||
|
||
/** | ||
* @brief Flag indicating that the member list is specified at create time | ||
* | ||
* @type bool | ||
* @flags CREATE_ONLY | ||
* @default false | ||
*/ | ||
SAI_IPMC_GROUP_ATTR_IPMC_GROUP_WITH_MEMBERS, | ||
|
||
/** | ||
* @brief IPMC output list | ||
* | ||
* @type sai_object_list_t | ||
* @flags CREATE_AND_SET | ||
* @objects SAI_OBJECT_TYPE_NEXT_HOP | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. why only nexthop, IPMC member create support RIF, Tunnel also There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. IIUC the object list check requires the list to contain a single object type.. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. object list can not have mix of object types. Only type sai_object_id_t can be of any types of object as specified in @objects |
||
* @default empty | ||
* @validonly SAI_IPMC_GROUP_ATTR_IPMC_GROUP_WITH_MEMBERS == true | ||
*/ | ||
SAI_IPMC_GROUP_ATTR_IPMC_OUTPUT_LIST, | ||
|
||
/** | ||
* @brief End of attributes | ||
*/ | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per your design, NOS should send all members during SET so that SAI can replace all existing members, that is not captured here