The question about languages mixes three very different spaces.
1) Is the format of a (potentially binary) packet on the wire, in this
case the trace log syntax.
2) Is the data model for the command exchanges.
3) Is the language used for information modeling.
Taking them in reverse order, ABNF (or RBNF) is absolutely the wrong
thing to use for item 3. I would prefer to use UML. If we decide (as
seems likely) to use YANG for the data modeling, then I can live with
skipping the UML step and going directly to YANG.
Item (2) is the domain of the protocol discussion the chairs are trying
to wrap up. I expect the mailing list to endorse the conclusion that we
should use YANG for this.
Item 1 could be seen as similar to item 2. But only if you constrain
the format to match what YANG can talk about. In describing a general
format (with details of the final binding to the wire deferred or
specified as we choose) ABNF / RBNF are very well suited to this
problem. And produce very clear descriptions of packets.
Yours,
Joel
On 4/15/14, 3:02 PM, Gonzalo Salgueiro (gsalguei) wrote:
As Joe mentioned, we're certainly open to expanding to UTF-8. To your (valid)
point regarding YANG, would the group prefer to see the trace log syntax expressed
in YANG instead of ABNF? We stuck with BNF-based out of sheer habit. If we did
this, for the sake of consistency, would we also want the syntax updated
(RBNF->YANG) in Nitin's RIB IM draft as well?
Gonzalo
On Apr 14, 2014, at 8:01 PM, Jeffrey Haas <[email protected]> wrote:
Authors,
While reviewing draft-clarke-i2rs-traceability, one big thing jumped out at
me that will require a bit more consideration: ABNF is only ASCII-friendly.
Since one of the data modeling languages we're considering is Yang, we need
to have support for unicode (UTF-8, e.g.).
I don't have a specific suggested fix at this time. I suspect this is a
bigger issue than just ours as it impacts other consumers of ABNF.
-- Jeff
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
