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 driving the actions of the
      Client.  The Client may not provide this identifier to the Agent
      if there is no external actor driving the Client.  However, this
      field MUST be logged.  If the Client does not provide an actor ID,
      then the Agent MUST log an empty field.
I can see that Actor ID can be useful to report back to Client operator about 
rouge Actor. WRT logging Actor ID, when the Actor ID is not provided by Client, 
instead of logging an empty field, I would suggest to log UNKNOWN or NOT FOUND 
or NOT PROVIDED, as it is easier to search for a keyword then just empty field.

Dean

On Apr 15, 2014, at 9:44 AM, Joe Marcus Clarke <[email protected]> wrote:

> 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 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.
> 
> Thanks for the feedback, Jeff!  We've been waiting for some :-).  Yes, ABNF 
> is ASCII-friendly.  When we originally wrote this, we were going off of what 
> was in the architecture.  I have some updates planned for this, and I will 
> work on updating the model to reflect current WG status.
> 
> Any other comments or suggestions are very much welcome.
> 
> Joe
> 
> _______________________________________________
> i2rs mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/i2rs
> 
> 


_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs

Reply via email to