Skip to content

Add attribute to signal estimated TLS activation time.#740

Open
HansBusch wants to merge 2 commits into
developmentfrom
feature/tls-switch-time
Open

Add attribute to signal estimated TLS activation time.#740
HansBusch wants to merge 2 commits into
developmentfrom
feature/tls-switch-time

Conversation

@HansBusch

Copy link
Copy Markdown
Member

No description provided.

</xs:attribute>
<xs:attribute name="SetupDuration" type="xs:duration">
<xs:annotation>
<xs:documentation>Indication how long a change to the TLS server settings need to be activated.</xs:documentation>

@bsriramprasad bsriramprasad Mar 13, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<xs:documentation>Indication how long a change to the TLS server settings need to be activated.</xs:documentation>
<xs:documentation>Indicates the maximum time taken for updated TLS server settings to take effect.</xs:documentation>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cappentz suggests to add 'maximum' time it takes

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@HansBusch I agree with this comment update also.

@kieran242

Copy link
Copy Markdown
Contributor

@HansBusch it would be good if you could add a description to the PR. Kind thanks

Comment thread wsdl/ver10/advancedsecurity/wsdl/advancedsecurity.wsdl
@ocampana-videotec

Copy link
Copy Markdown
Collaborator

@HansBusch I am a bit lost on this PR. In what state is this? Are you still targeting 26.06 or can we move this to 26.12?

@HansBusch

Copy link
Copy Markdown
Member Author

@HansBusch I am a bit lost on this PR. In what state is this? Are you still targeting 26.06 or can we move this to 26.12?

We didn't close last week. Hence I suggest to defer to 26.12.

Comment thread doc/Security.xml
</row>
<row>
<entry>SetupDuration</entry>
<entry><para>Indication how long a change to the TLS server configuration needs to be activated.</para></entry>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • It is ambiguous whether the value means:
    • time until the change becomes active, or
    • time for which the change remains active, or
    • time required after activation
Suggested change
<entry><para>Indication how long a change to the TLS server configuration needs to be activated.</para></entry>
<entry><para>Indicates how long a TLS server configuration change takes to become effective..</para></entry>

@ocampana-videotec ocampana-videotec modified the milestones: 26.06, 26.12 Jun 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify switching TLS configuration with ReplaceServerCertificateAssignment

5 participants