Re: [netconf] Capability-fetching mechanisms

[Mahesh Jethanandani <[e-mail]>]

Hi Qin,

Thank you for sharing an example. We now understand better what was intended. After discussing some, three things come to mind.

1) We do not have a particular requirement for an off-line format, and find it an unnecessary overhead of having to wrap the data with yang-instance-data.

2) There seems to be an implication of the receiver being a NETCONF server, something that we made an effort to avoid in the first place. 

3) The data export capabilities other leafs that we do not care about. How do we restrict the response to data that is pertinent to our transport draft? In the example you shared, we see capabilities for udp-notif being returned in addition to http-notif.

For these reasons, we feel the that the value proposition is limited, while increasing complexity.

Mahesh & Kent



> On Jun 15, 2021, at 5:27 AM, Qin Wu <[e-mail]> wrote:
> 
> [Qin Wu] Here is the example:
>    The publisher can send the following request to learn the receiver
>    capabilities.
>  
>    GET HTTP 1.1 /some/path/capabilities/acme-receiver-capabilities.json
>    Host: example.com <http://example.com/>
>    Accept: application/xml, application/json
>    If the receiver is unable to reply using "application/xml", 
> the response might look like this:
>    HTTP/1.1 200 OK
>    Date: Wed, 26 Feb 2020 20:33:30 GMT
>    Server: example-server
>    Cache-Control: no-cache
>    Content-Type: application/json
>    Content-Length: nnn
>  
>    {
>      "ietf-yang-instance-data:instance-data-set": {
>        "name": "acme-receiver-capabilities",
>        "content-schema": {
>          "module": "ietf-data-export-capabilities"
>        },
>        "timestamp": "2018-01-25T17:00:38Z",
>        "description": [
>          "Receiver capability"
>        ],
>        "content-data": {
>          "system-capabilities": {
>            "ietf-data-export-capabilities:data-export-capabilities": [
>              {
>                "transport-protocol": "http-notif",
>                "encoding-format": [
>                  "json",
>                  "xml",
>                  "rfc8639-enabled"
>                ]
>              },
>              {
>                "transport-protocol": "udp-notif",
>                "encoding-format": [
>                  "binary"
>                ]
>              }
>            ]
>          }
>        }
>      }
> }