[rpp] Re: [dconn] DomainConnect Async flow spec

[[e-mail]]

Now to the right WG. @rpp WG sorry for spam.

Kind Regards,
Pawel

On 19.03.26 13:24, Pawel Kowalik wrote:
>
> Thank you Liana.
>
> Today in the session the WG discussed splitting out async flow to a 
> separate draft.
>
> I will cover this change in this new draft dedicated to async.
>
> Kind Regards,
> Pawel
>
> On 18.03.26 08:44, Liana Maria Panatau wrote:
>> Hi Pawel,
>>
>> I think it is a good idea to have a clear distinction regarding which 
>> parameters go where. And keeping the built-in parameters as query 
>> parameters and the other template variables in the JSON body seems 
>> very reasonable.
>> For example, including the domain name in the query string makes 
>> debugging easier and is also compatible with the synchronous flow. 
>> This is an advantage I can think of.
>>
>>
>> Best Regards,
>> Liana
>>
>> On Wed, Feb 18, 2026 at 6:35 PM Pawel Kowalik 
>> <kowalik=[e-mail]> wrote:
>>
>>     Hi Liana,
>>
>>     thanks this is very useful.
>>
>>     It was brought up in Httpdir review already [1] and I was more of
>>     the opinion that dropping body variant would be a better option.
>>
>>     With your input it seems that the opposite shall be the case,
>>     which would be more appropriate for POST call. Supporting both
>>     would have a clear issue of precedence and (potentially)
>>     parameter merging that needs to be clearly specified. Choosing
>>     one shall be therefore of benefit. It would be a breaking change
>>     - however for minority of async clients.
>>     Or do you see a value of supporting both but with a clear
>>     distinction which parameters go where (e.g. built-in parameters
>>     domain/host etc. in query string and only template variables in
>>     JSON body)?
>>
>>     Kind Regards,
>>     Pawel
>>
>>     [1]
>>     https://mailarchive.ietf.org/arch/msg/dconn/OdpMymC2VQaqxL5i4gw8VrLMbyw/
>>     # 7.3.6.
>>
>>     On 18.02.26 07:21, Liana Maria Panatau wrote:
>>>     Hello,
>>>
>>>     I’m part of the IONOS team managing the Domain Connect platform.
>>>     Following a discussion with Pawel about our experience with the
>>>     asynchronous flow, I’d like to raise some concerns regarding the
>>>     async flow spec, specifically about the apply endpoint.
>>>
>>>     Currently, service providers using the async flow pass template
>>>     parameters via query parameters. We've encountered many issues
>>>     with this approach:
>>>     - Encoding issues (frequent bugs related to URL encoding/decoding)
>>>     - URL too long exception because of too many query parameters
>>>
>>>     We are looking into supporting the request body for template
>>>     parameters, but we want to ensure we handle edge cases correctly:
>>>     - How should we handle conflicts between query parameters and
>>>     the body? Which input has priority?
>>>     - Should we support merging parameters from both sources, or
>>>     reject "fragmented" requests?
>>>
>>>     In our view, a cleaner approach would be to restrict template
>>>     parameters to the request body only and maybe accept some
>>>     specific query parameters clearly defined in the spec.
>>>
>>>     Looking forward to your feedback.
>>>     -- 
>>>
>>>     Liana Maria Panatau
>>>
>>>     Sr. Staff Software Engineer
>>>     Domains Retail Platform Development
>>>
>>>     IONOS S.R.L. | 246C Calea Floreasca | 077190 Bucuresti | Romania
>>>     E-Mail: [e-mail] | Web: www.ionos.com
>>>     <https://www.ionos.com>
>>>
>>>     General information about the company can be foundhere
>>>     <https://www.ionos.com/about>.
>>>
>>>     A member of the IONOS Group
>>>
>>>
>>>     _______________________________________________
>>>     dconn mailing list [e-mail]
>>>     To unsubscribe send an email [e-mail]
>>
>>
>>
>> -- 
>>
>> Liana Maria Panatau
>>
>> Sr. Staff Software Engineer
>> Domains Retail Platform Development
>>
>> IONOS S.R.L. | 246C Calea Floreasca | 077190 Bucuresti | Romania
>> E-Mail: [e-mail] | Web: www.ionos.com 
>> <https://www.ionos.com>
>>
>> General information about the company can be foundhere 
>> <https://www.ionos.com/about>.
>>
>> A member of the IONOS Group
>>
>
> _______________________________________________
> rpp mailing list [e-mail]
> To unsubscribe send an email [e-mail]