Open APIs

 View Only

  • 1.  Use of OASIS or similar frameworks to prevent replay requests in TM Forum Open APIs

    TM Forum Member
    Posted 27 days ago

    Hi all,

    Has TM Forum ever considered including support for frameworks like OASIS (or similar alternatives) in the Open API specifications?

    OASIS (Open API Specification for Idempotency Support) defines patterns to ensure that duplicate requests (retries) are not processed multiple times by the backend. This is especially useful in distributed systems and long-running operations, which are both common scenarios in the TM Forum ecosystem.

    Given the critical role that idempotency and reliability play in order management and service/resource orchestration and activation, I was wondering if there's been any discussion around this, or if it's part of the roadmap.

    Best regards,



    ------------------------------
    Abel Ruiz Huerta
    alvatross
    ------------------------------


  • 2.  RE: Use of OASIS or similar frameworks to prevent replay requests in TM Forum Open APIs

    TM Forum Member
    Posted 26 days ago

    There is a similar RFC draft: https://datatracker.ietf.org/doc/draft-ietf-httpapi-idempotency-key-header/

    And a corresponding discussion how this aligns with the OASIS framework: https://github.com/ietf-wg-httpapi/idempotency/issues/31

    So maybe we should wait until this has been resolved?



    ------------------------------
    Lutz Bettge
    Deutsche Telekom AG
    ------------------------------

    Original Message


  • 3.  RE: Use of OASIS or similar frameworks to prevent replay requests in TM Forum Open APIs

    TM Forum Member
    Posted 22 days ago
    I would definitely like to see the TMF OpenAPI group address the general issue. Today, we try to mitigate this problem differently when using TMF OpenAPIs, but this is not possible for all APIs.
     
    However, I'm not sure how long we should wait for the IETF approach here. The first draft is from 2020. I know the wheels at the IETF turn slowly, but the OASIS draft seems to me to be much more "stable". After all, the OASIS specification has already been published in version 1.0 and no longer has draft status. The corresponding headers are already assigned at IANA. However, there don't seem to be many implementations here yet, but I was able to quickly discover an Azure service that already implements this.
     
    Regards,
    Jan


    ------------------------------
    Jan Lemmermann
    OSS Lead Architect
    EWE TEL GmbH
    ------------------------------

    Original Message