Re: [Taps] Early TAPS Implementation in Go, Feedback Welcome

[Mirja Kuehlewind <[e-mail]>]

Hi Troben,

thanks for sharing and using the taps API. For the mistakes you found I recommend to open issues on github or even create a PR if the resolution is straight-forward: https://github.com/ietf-tapswg

Mirja


On 04.01.22, 15:18, "Taps on behalf of Thorben Krüger" <[e-mail] on behalf of [e-mail]> wrote:

    Dear TAPS,

    In the context of a recently started EU NGI Pointer project[1], we 
    are currently involved in engineering[2] an open source transport 
    services system in Go, with support for SCION[4], a 
    next-generation path-aware Internet architecture, enabling 
    multi-path communication at the inter-domain level.

    Our system, called PANAPI[3] (Path-Aware Networking API), aims to 
    hide complex automated processes (such as protocol racing) behind 
    convenient high-level abstractions. In the backend, PANAPI 
    consists of a (Lua) scriptable framework to support practical path 
    selection in the context of the SCION architecture. (We also aim 
    to provide UDP, TCP/IP and QUIC support, but achieving full 
    RFC8923[5] compliance is only a secondary goal.)

    To avoid re-inventing the wheel on the frontend-side, we have 
    chosen to adopt the abstractions laid out in the current TAPS 
    Interface draft[6]. Most of these could be easily mapped to our Go 
    implementation, but in a few cases we decided to depart from the 
    specification. We are unsure to what degree our decisions[7] are 
    in violation of the TAPS vision and would appreciate feedback, 
    especially from folks who have some familiarity with Go.

    Note that this email is not intended to announce a fait 
    accompli. PANAPI is still under development and only partially 
    usable in its current state. The user-facing API[8] is about two 
    thirds done, and we would be glad to incorporate your feedback on 
    our implementation choices[7]. While Candidate Gathering and 
    Candidate Racing are still waiting to be implemented, the main 
    SCION-based, scriptable path-selection framework for the backend 
    is nearly complete. We would highly appreciate any kind of 
    contributions, even only informal feedback, also from non-Go 
    programmers.

    Finally, we believe we have identified a few minor mistakes in the 
    Interface draft[6]. What is the proper process of discussing 
    these?

    Kind regards and happy new year,

    Thorben Krüger
    Otto-von-Guericke University, Magdeburg

    [1]: https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-dfd3bd71b085b967&q=1&e=f73004e3-6a0b-487f-b306-baac8445e614&u=https%3A%2F%2Fwww.ngi.eu%2Ffunded_solution%2Fngi-pointer-project-33%2F
    [2]: https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-a6202abfcbbafaa4&q=1&e=f73004e3-6a0b-487f-b306-baac8445e614&u=https%3A%2F%2Fgithub.com%2Fnetsys-lab%2Fpanapi%2Ftree%2Ftaps
    [3]: https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-e2435aed8f4e8766&q=1&e=f73004e3-6a0b-487f-b306-baac8445e614&u=https%3A%2F%2Fdl.acm.org%2Fdoi%2F10.1145%2F3472727.3472808
    [4]: https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-9249a3ce4b132d30&q=1&e=f73004e3-6a0b-487f-b306-baac8445e614&u=https%3A%2F%2Fscion-architecture.net%2F
    [5]: https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-20505ec0daf0d7ae&q=1&e=f73004e3-6a0b-487f-b306-baac8445e614&u=https%3A%2F%2Fwww.rfc-editor.org%2Frfc%2Frfc8923.html
    [6]: 
    https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-76cbc5967efb114d&q=1&e=f73004e3-6a0b-487f-b306-baac8445e614&u=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-taps-interface-13.html
    [7]: 
    https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-367b4fc5664866f3&q=1&e=f73004e3-6a0b-487f-b306-baac8445e614&u=https%3A%2F%2Fgithub.com%2Fnetsys-lab%2Fpanapi%2Fblob%2Ftaps%2Fdoc%2FImplementation.md
    [8]: 
    https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-9fd94feaea2ba82d&q=1&e=f73004e3-6a0b-487f-b306-baac8445e614&u=https%3A%2F%2Fpkg.go.dev%2Fgithub.com%2Fnetsys-lab%2Fpanapi%40v0.3.0-alpha7%2Ftaps

    PS: PANAPI receives official funding from NGI Pointer[1]

    _______________________________________________
    Taps mailing list
    [e-mail]
    https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-a4d4eb0115e9372f&q=1&e=f73004e3-6a0b-487f-b306-baac8445e614&u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Ftaps