Re: [netconf] netconf-https-notif-draft HTTP "pipelining"

Hi,

The problem I see with the "bundled messages" method is that it seems
to transmit the URL once... which contains an important part of the
Restconf Semantics... that feels like a strange restriction and
something easy to get wrong.

Henning

On Fri, Jan 22, 2021 at 8:47 PM Reshad Rahman <reshad@yahoo.com> wrote:
>
> Hi Mahesh,
>
>
>
> Since draft-ietf-netconf-notification-messages is in parked state, and expired 8 months ago, should the netconf-https-notif document be using bundled messages? But I don’t know the reason why it’s in parked state and whether it’ll be in drive mode soon.
>
>
>
> Regards,
>
> Reshad.
>
>
>
> From: netconf <netconf-bounces@ietf.org> on behalf of Mahesh Jethanandani <mjethanandani@gmail.com>
> Date: Friday, January 22, 2021 at 2:08 PM
> To: Henning Rogge <hrogge@gmail.com>
> Cc: Netconf <netconf@ietf.org>
> Subject: Re: [netconf] netconf-https-notif-draft HTTP "pipelining"
>
>
>
> Hi Henning,
>
>
>
> The draft was trying to address the question of “pipelining” using two methods. One is the equivalent of “HTTP 1.1 pipelining” and the other is concept of “bundled-messages” introduced by draft-ietf-netconf-notification-messages. In the process it mixed both of them, and thus the contradiction in the example in section 1.5.1.
>
>
>
> Let me update the document to fix the example(s), at which point the WG can decide if they want to support one or both the methods.
>
>
>
> Thanks.
>
>
>
> On Jan 13, 2021, at 11:29 PM, Henning Rogge <hrogge@gmail.com> wrote:
>
>
>
> Hi,
>
> I had a longer discussion with Kent Watsen yesterday and he asked me
> to get the questions about the netconf-https-notif-draft to the
> mailing list:
>
> In section 1.5.1 the draft talks about "pipelining" of messages. Is
> this meant equivalent to "HTTP 1.1 pipelining" or is this just a
> technique unique to the draft? If this is not something reused from
> HTTP, maybe there should be some advice on how this interacts with
> normal HTTP server/client code.
>
> Also the example in 1.5.1 seems to contradict each other.
>
> The overview (page 5) shows the Publisher sending HTTPS POST message
> once for each notification (which I think is important because the URL
> is part of the context of the message)... but the content description
> (page 6) does only show a single POST with multiple responses. Same is
> true for chapter 8.3.
>
> Henning Rogge
>
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>
>
>
> Mahesh Jethanandani
>
> mjethanandani@gmail.com
>
>
>
>
>
>
>
>
>
> _______________________________________________ netconf mailing list netconf@ietf.org https://www.ietf.org/mailman/listinfo/netconf