BLS Signatures
draft-irtf-cfrg-bls-signature-05
Revision differences
Document history
| Date | Rev. | By | Action |
|---|---|---|---|
|
2022-12-18
|
05 | (System) | Document has expired |
|
2022-06-16
|
05 | Riad Wahby | New version available: draft-irtf-cfrg-bls-signature-05.txt |
|
2022-06-16
|
05 | Riad Wahby | New version accepted (logged-in submitter: Riad Wahby) |
|
2022-06-16
|
05 | Riad Wahby | Uploaded new revision |
|
2021-03-14
|
04 | (System) | Document has expired |
|
2020-09-10
|
04 | Riad Wahby | New version available: draft-irtf-cfrg-bls-signature-04.txt |
|
2020-09-10
|
04 | (System) | New version accepted (logged-in submitter: Riad Wahby) |
|
2020-09-10
|
04 | Riad Wahby | Uploaded new revision |
|
2020-09-10
|
03 | Riad Wahby | New version available: draft-irtf-cfrg-bls-signature-03.txt |
|
2020-09-10
|
03 | (System) | New version accepted (logged-in submitter: Riad Wahby) |
|
2020-09-10
|
03 | Riad Wahby | Uploaded new revision |
|
2020-09-10
|
02 | (System) | Document has expired |
|
2020-09-08
|
02 | Alexey Melnikov | |
|
2020-03-09
|
02 | Riad Wahby | New version available: draft-irtf-cfrg-bls-signature-02.txt |
|
2020-03-09
|
02 | (System) | New version accepted (logged-in submitter: Riad Wahby) |
|
2020-03-09
|
02 | Riad Wahby | Uploaded new revision |
|
2020-03-09
|
01 | Riad Wahby | New version available: draft-irtf-cfrg-bls-signature-01.txt |
|
2020-03-09
|
01 | (System) | New version accepted (logged-in submitter: Riad Wahby) |
|
2020-03-09
|
01 | Riad Wahby | Uploaded new revision |
|
2020-02-13
|
00 | (System) | Document has expired |
|
2019-08-12
|
00 | Nick Sullivan | This document now replaces > requests have the additional attributes described in the list below. MSCML Response Attributes for <playcollect>: o reason … This document now replaces > requests have the additional attributes described in the list below. MSCML Response Attributes for <playcollect>: o reason - optional, no default value: For requests that do not complete immediately, the "reason" attribute conveys additional information regarding why the command completed. Possible values are "stopped", indicating an explicit or implicit <stop> request was received, "match" meaning a DTMF grammar was matched, Van Dyke, et al. Expires December 21, 2006 [Page 54] Internet-Draft MSCML June 2006 "timeout" indicating that no DTMF input was received before one of the collection timers expired, and "returnkey" or "escapekey" meaning the DTMF digit mapped to that key was detected. the return key or escape key terminated the operation, respectively. o playduration - required, no default value: A time value (Section 4.2.1) that returns the duration of the associated content playout. If the caller barged the prompt this value will reflect the play duration up to that event. o playoffset - required, no default value: A time value (Section 4.2.1) that returns the time offset into the specified content sequence where play was terminated. If the initial "offset" value in the sequence was "0", then "playduration" and "playoffset" are equal. However, if the the initial offset had some other value "playoffset" serves as a bookmark for the client to resume play in a subsequent request. If the caller barged the prompt this value will reflect the time offset at which barge-in occurred. o digits - required, no default value: Contains the collected DTMF input characters. If no DTMF input was collected this attribute is set to the empty string (""). o name - required (see note), no default value: The client defined name of the DTMF grammar that was matched. Note: This attribute is required if the "name" attribute was set in the matching DTMF grammar. Responses to <playcollect> requests MAY include an <error_info> element as described in Section 10.4.1. 10.6. Response Attributes and Elements for <playrecord> In addition to the base response attributes defined in Section 10.2, responses to <playrecord> requests have the additional attributes described in the list below. o reason - optional, no default value: For requests that do not complete immediately, the "reason" attribute conveys additional information regarding why the command completed. Possible values are "stopped", indicating an explicit or implicit <stop> request was received, "digit" meaning a DTMF digit was detected so the prompt phase was barged, "init_silence" meaning the recording terminated because because of no input, "end_silence" meaning the recording was terminated because the "endsilence" timer elapsed, "max_duration" indicating that the maximum time for the recording was reached, "escapekey" indicating the DTMF input mapped to "escapekey" was detected, thus terminating the recording and "error" indicating a general operation failure. Van Dyke, et al. Expires December 21, 2006 [Page 55] Internet-Draft MSCML June 2006 o playduration - required, no default value: A time value (Section 4.2.1) that returns the duration of the associated content playout. If the caller barged the prompt this value will reflect the play duration up to that event. o playoffset - required, no default value: A time value (Section 4.2.1) that returns the time offset into the specified content sequence where play was terminated. If the initial "offset" value in the sequence was "0", then "playduration" and "playoffset" are equal. However, if the the initial offset had some other value "playoffset" serves as a bookmark for the client to resume play in a subsequent request. If the caller barged the prompt this value will reflect the time offset at which barge-in occurred. o digits - required, no default value: Contains the DTMF digit that terminated the recording. If no DTMF input was detected this attribute is set to the empty string (""). o reclength - required, no default value: The length of the recorded content in bytes. o recduration - required, no default value: A time value (Section 4.2.1) indicating the elapsed duration of the recording. Responses to <playrecord> requests MAY include an <error_info> element as described in Section 10.4.1. 10.7. Response Attributes and Elements for <managecontent> Responses to <managecontent> requests have only the base response attributes defined in Section 10.2. If a content transfer error occurs while executing the request the response will also contain an <error_info> element as described in Section 10.4.1. 10.8. Response Attributes and Elements for <faxplay> and <faxrecord> In addition to the base response attributes defined in Section 10.2, responses to <faxplay> and <faxrecord> requests have the additional attributes described in the list below. o reason - required, no default value: For requests that do not complete immediately, the "reason" attribute conveys additional information regarding why the command completed. Possible values are "stopped", indicating an explicit or implicit <stop> request was received, "complete" indicating successful completion, even if there were bad lines or minor negotiation problems (e.g. a DCN was received), "disconnect" meaning that the session was disconnected and "notfax" indicating that no DIS or DCS was received on the connection. Van Dyke, et al. Expires December 21, 2006 [Page 56] Internet-Draft MSCML June 2006 draft-boneh-bls-signature instead of None |
|
2019-08-12
|
00 | Nick Sullivan | Intended Status changed to Informational from None |
|
2019-08-12
|
00 | Zhenfei Zhang | New version available: draft-irtf-cfrg-bls-signature-00.txt |
|
2019-08-12
|
00 | (System) | WG -00 approved |
|
2019-08-11
|
00 | Zhenfei Zhang | Set submitter to "Zhenfei Zhang ", replaces to (none) and sent approval email to group chairs: cfrg-chairs@ietf.org |
|
2019-08-11
|
00 | Zhenfei Zhang | Uploaded new revision |