Section 6.1: Persistence of HMAC-ALGO parameter

[tuexen]

An SCTP endpoint MUST NOT change the parameters listed in the HMAC-ALGO parameter during the lifetime of the endpoint.

I think it is unclear what is meant with a lifetime of the endpoint here. I can understand that this would apply for the life time of the SCTP association, but for the life time of the endpoint appears to limiting. I think that this preference list should be bound to a shared key. Thus, if one generate new endpoint pair shared key, one can have a different preference list when using that key?

This was reported in Comments on draft-tuexen-tsvwg-rfc4895-bis-04.

[tuexen]

An SCTP endpoint MUST NOT change the parameters listed in the HMAC-ALGO parameter during the lifetime of the endpoint.

I think it is unclear what is meant with a lifetime of the endpoint here. I can understand that this would apply for the life time of the SCTP association, but for the life time of the endpoint appears to limiting. I think that this preference list should be bound to a shared key. Thus, if one generate new endpoint pair shared key, one can have a different preference list when using that key?

But the list is announced by both endpoints during association setup. So it can' be changed dynamically. Choosing the preference is also done at receiver side, not sender side. So I don't know how to do this when endpoint shared keys are configured. I also don't understand the use case of making the selection per endpoint shared secret.
@gloinul : Could you elaborate?

This was reported in Comments on draft-tuexen-tsvwg-rfc4895-bis-04.