On 4/14/14, 8:01 PM, Jeffrey Haas 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
Joe,
Besides having the same comment as Jeff, here is one more and think some
additional clarification is needed
Actor Identifier: This is an opaque identifier that may be known to
the Client from a northbound controlling application. This is
used to trace the northbound actor
On 4/15/14, 2:09 PM, Dean Bogdanovic wrote:
Joe,
Besides having the same comment as Jeff, here is one more and think some
additional clarification is needed
Actor Identifier: This is an opaque identifier that may be known to
the Client from a northbound controlling application. This
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 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,
