Re: [netconf] HTTPS notifications (draft-ietf-netconf-https-notif)

[Kent Watsen <[e-mail]>]

Hi Balazs,


> The draft should discuss how long the HTTPS connection is held open for the next notification. Or is it open/closed for each notification?

Should it?  Perhaps it should say "Implementations must determine how long the HTTPS connection is held open for subsequent notifications, or if it is open/closed for each notification."


>  The draft should include a sequence diagram showing the message flow something like:
> Server                         Client
> <------- establish TCP
> <------- establish SSH (or TLS)
> <------- establish Netconf session
> <------- <edit-config>   configure subscription over Netconf
> <-------- <close-session>
> <-------- tear down Netconf/SSH/TCP

I don't think the draft needs to include this diagram, as it's standard NETCONF.


> Later
>  
> ------> establish TCP
> ------> establish TLS
> ------> Send HTTPS POST message with YANG defined notification
> <-----Send OK
>  
> The last 2 or 4 steps repeat until the subscription is removed by another <edit-config> 


Assuming the TLS session is help open, it might look like this?

> ------> establish TCP
> ------> establish TLS
> ------> Send HTTPS POST message with YANG defined notification
> <-----Send 204 (No Content)
> ------> Send HTTPS POST message with YANG defined notification
> <-----Send 204 (No Content)

> ------> Send HTTPS POST message with YANG defined notification
> <-----Send 204 (No Content)



From the email I sent Martin on Sep 9th, each POST MAY contain more than one notification:


    POST /some/path HTTP/1.1
    Host: my-receiver.my-domain.com <http://my-receiver.my-domain.com/>
    Content-Type: application/yang-data+xml

    <notification
      xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
      <eventTime>2019-03-22T12:35:00Z</eventTime>
      <foo xmlns="https://example.com <https://example.com/>/my-foobar-module">
        ...
      </foo>
    </notification>

    <notification
      xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
      <eventTime>2019-03-22T12:35:00Z</eventTime>
      <bar xmlns="https://example.com <https://example.com/>/my-foobar-module">
        ...
      </bar>
    </notification>

    <notification
      xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
      <eventTime>2019-03-22T12:35:00Z</eventTime>
      <baz xmlns="https://example.com <https://example.com/>/my-foobar-module">
        ...
      </baz>
    </notification>


With response:

      HTTP/1.1 204 No Content
      Date: Thu, 26 Jan 2017 20:56:30 GMT
      Server: my-receiver.my-domain.com <http://my-receiver.my-domain.com/>


Kent // co-author