Re: [irs-discuss] irs problem statement

Thanks for the pointers - I saw them on the agenda for NetConf as well.

As I said to Joel, we need to agree and focus on agreeing on the
problem-statement and use-cases before trying to pin down particular
protocol(s).

Hearing more feedback though about how well NetConf does or could meet
the needs and suggested requirements is quite interesting.

Alia

On Mon, Jul 30, 2012 at 7:30 PM, Vytautas Valancius <valas@google.com> wrote:
>> URL:             http://www.ietf.org/internet-drafts/draft-atlas-irs-problem-statement-00.txt
>> Status:          http://datatracker.ietf.org/doc/draft-atlas-irs-problem-statement
>> Htmlized:        http://tools.ietf.org/html/draft-atlas-irs-problem-statement-00
>
> Nitpick:
>
> "The transport mechanisms that are currently defined (e.g., SOAP/BEEP)
> for NetConf are not those commonly used by modern applications (e.g.,
> ReST or JSON)."
>
> Technically correct, but, FYI, there is active work going on to make
> NetConf and YANG REST and JSON friendly:
> http://tools.ietf.org/html/draft-bierman-netconf-yang-api-00
> http://tools.ietf.org/html/draft-lhotka-yang-json-00
>
> Regards,
> Valas
> _______________________________________________
> irs-discuss mailing list
> irs-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/irs-discuss