Feature: radio-signal-id (Trail trace identifier (TTI))

[demx8as6]

This issue is related to #22 and should address the following ONF parameters:

 +--ro air-interface:supported-radio-signal-id-datatype?            radio-signal-id-datatype-type   x
 +--ro air-interface:supported-radio-signal-id-length?              int16   x
 +--ro air-interface:expected-equals-transmitted-radio-signal-id?   boolean x
 +--rw air-interface:transmitted-radio-signal-id    x
 |  +--rw air-interface:numeric-radio-signal-id?        int32   x
 |  +--rw air-interface:alphanumeric-radio-signal-id?   string  x
 +--rw air-interface:expected-radio-signal-id   x
 |  +--rw air-interface:numeric-radio-signal-id?        int32   x
 |  +--rw air-interface:alphanumeric-radio-signal-id?   string  x
 +--ro air-interface:received-radio-signal-id   x
 |  +--ro air-interface:numeric-radio-signal-id?        int32   x
 |  +--ro air-interface:alphanumeric-radio-signal-id?   string  x
 |  +--rw signalling-format?    string  x

Feature description.

There should be a to transmit a configurable ID to the receiver. if the receiver detects a mismatch between the received and expected ID an alarm should be raised.

personal remarks: The alarm is also known as "Trail trace identifier (TTI) mismatch" in OTN - ITU-T G.709/Section 15.2

I could not find in IETF a related model

A similar model can be found in openconfig: https://github.com/openconfig/public/blob/master/release/models/optical-transport/openconfig-terminal-device.yang#L481

[demx8as6]

for further discussion a "working-document-yang-model" should be created -> AP: Martin for 2023-12-07

[demx8as6]

Proposed solution:

module: ietf-onf-gab-discussion

  augment /if:interfaces/if:interface:
    +--rw trail-trace-identifier {trail-trace-identifier}?
       +--rw receiver
       |  +--rw trail-trace-identifier-expected
       |  |  +--rw source-access-point-identifier         access-point-identifier
       |  |  +--rw destination-access-point-identifier    access-point-identifier
       |  |  +--rw operator-specific                      string
       |  +--ro trail-trace-identifier-received
       |  |  +--ro source-access-point-identifier         access-point-identifier
       |  |  +--ro destination-access-point-identifier    access-point-identifier
       |  |  +--ro operator-specific                      string
       |  +--ro status?                            enumeration
       +--rw transmitter
          +--rw trail-trace-identifier-transmitted
             +--rw source-access-point-identifier         access-point-identifier
             +--rw destination-access-point-identifier    access-point-identifier
             +--rw operator-specific                      string

Please see: ietf-onf-gab-discussion.yang ietf-onf-gab-discussion.yang.txt

[samans]

Review the models from ITU-T Q14. Suggest moving this feature to if-ext draft.

How does this apply to microwave? Is there an example that could be added in the Radio Link Draft? In microwave, this feature would be used to determine if the radio on one side is talking to the expected radio on the other side.

Further discussion on the formatting of the ids is needed.

[DanielaSpreafico]

For microwave links (point to point connections) the source-access-point-identifier and destination-access-point-identifier are not needed.

[demx8as6]

As discussed almost 2 weeks ago we can simplify the TTIs like this:

  augment /if:interfaces/if:interface:
    +--rw trail-trace-identifier {trail-trace-identifier}?
       +--rw receiver
       |  +--rw trail-trace-identifier-expected?   trail-trace-identifier-type
       |  +--ro trail-trace-identifier-received?   trail-trace-identifier-type
       |  +--ro status?                            enumeration
       +--rw transmitter
       |  +--rw trail-trace-identifier-transmitted?   trail-trace-identifier-type
       +--rw rx-enabled?         boolean
       +--ro rx-oper-status?     oper-status
       +--rw cryptographic {cryptographic}?
       |  +--rw enabled?             boolean
       |  +--rw symmetric-key-ref    ks:central-symmetric-key-ref

with a typedef like this:

  typedef trail-trace-identifier-type {
    type union {
      type string {
        length "1..64";
      }
      type uint32;
    }
    description
      "An up to 64 byte string representing the trail trace identifier
       value, inspired by ITU-T. ";
    reference
      "ITU-T G709";
  }

It combines the needs of a string but also of a uint.

In any case such model should be part of the ietf-if-extension and should not be part of ietf-microwave-radio-link.

ietf-onf-gab-discussion.yang.txt

[samans]

Move this to the issue list of the ietf interface extensions work (netmod). https://datatracker.ietf.org/doc/html/draft-ietf-netmod-intf-ext-yang

[samans]

Review this again, and add as microwave specific extension.