[OASIS Issue Tracker] (DSSX-40) Public Comment 201809c00001s16

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/DSSX-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Hagen updated DSSX-40:
-----------------------------
    Description: 
Comments from TC ESI to OASIS DSS-X TC on DSS-X V2 - 16 of 19 submitted by Liaison Andreas Kuehne on behalf of Sonia Companies via message Â[201809c00001|http://lists.oasis-open.org/archives/dss-x-comment/201809/msg00001.html]Âper attachment with accessibility issues (word file)
{quote}following steering committee call on 17/09 and addition of 2 other editorial comments, the resulting pre-agreed comments are now for ESI approval for submission to OASIS DSS-X TC by 28 September
{quote}
h2. Comment #16:
|Clause 7
Â
QUESTION: in this model is the server the one that decides whether the management is done synchronous or asynchronous. Could it be possible to consider the possibility of allowing the client to have the possibility of deciding this?|
|AK: are there use cases for this?|
|FP, LR: there are few use cases for thisâfor instance when the client does not want to wait until the server finishes, but it prefers to leave this, do something else and come back later on. This is more for server to server communication.|
|AK: this is a good point and we should think about it.|
|JC: I guess that this would also impact the validation protocol, not only the sign protocol.|
|AK: indeed, clause 7 affects both.|
|CONCLUSION: Pass this request to DSS-X TC|

  was:
Comments from TC ESI to OASIS DSS-X TC on DSS-X V2 - 16 of 19 submitted by Liaison Andreas Kuehne on behalf of Sonia Companies via message Â[201809c00001|http://lists.oasis-open.org/archives/dss-x-comment/201809/msg00001.html]Âper attachment with accessibility issues (word file)
{quote}following steering committee call on 17/09 and addition of 2 other editorial comments, the resulting pre-agreed comments are now for ESI approval for submission to OASIS DSS-X TC by 28 September
{quote}
Â


> Public Comment 201809c00001s16
> ------------------------------
>
>                 Key: DSSX-40
>                 URL: https://issues.oasis-open.org/browse/DSSX-40
>             Project: OASIS Digital Signature Services eXtended (DSS-X) TC
>          Issue Type: Bug
>    Affects Versions: PRD01
>            Reporter: Andreas Kuehne
>            Priority: Major
>              Labels: PRD01_COMMENT, TC_ESI
>
> Comments from TC ESI to OASIS DSS-X TC on DSS-X V2 - 16 of 19 submitted by Liaison Andreas Kuehne on behalf of Sonia Companies via message Â[201809c00001|http://lists.oasis-open.org/archives/dss-x-comment/201809/msg00001.html]Âper attachment with accessibility issues (word file)
> {quote}following steering committee call on 17/09 and addition of 2 other editorial comments, the resulting pre-agreed comments are now for ESI approval for submission to OASIS DSS-X TC by 28 September
> {quote}
> h2. Comment #16:
> |Clause 7
> Â
> QUESTION: in this model is the server the one that decides whether the management is done synchronous or asynchronous. Could it be possible to consider the possibility of allowing the client to have the possibility of deciding this?|
> |AK: are there use cases for this?|
> |FP, LR: there are few use cases for thisâfor instance when the client does not want to wait until the server finishes, but it prefers to leave this, do something else and come back later on. This is more for server to server communication.|
> |AK: this is a good point and we should think about it.|
> |JC: I guess that this would also impact the validation protocol, not only the sign protocol.|
> |AK: indeed, clause 7 affects both.|
> |CONCLUSION: Pass this request to DSS-X TC|



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)