1. Pages
2. …
3. Open Transport Configuration and Control Home
4. 5G-xHaul
5. 5G-xHaul Call-in Details & Notes

2020-08-05 5G-xHaul Meeting notes

00:00

HTTP-POST:

url:

• /rests/operations/network-topology:network-topology/topology=topology-netconf/node=<mount-point-name>/yang-ext:mount/ietf-netconf:get

headers:

• Accept: application/xml
• Content-Type: application/json

body:

{ 
  "ietf-netconf:input": {
    "filter": {
      "core-model-1-4:control-construct": {
        "core-model-1-4:logical-termination-point": {
          "core-model-1-4:name": {
            "core-model-1-4:value-name" : "externalLabel"
          }
        }
      }
    }
  }
}

GET externalLabel from specific LTP

HTTP-GET:

url:

• /rests/data/network-topology:network-topology/topology=topology-netconf/node=<mount-point-name>/yang-ext:mount/core-model-1-4:control-construct/logical-termination-point=<ltp-uuid>/name=externalLabel

headers:

• Accept: application/yang-data+json

SET externalLabel in specific LTP

HTTP-PUT:

url:

• /rests/data/network-topology:network-topology/topology=topology-netconf/node=<mount-point-name>/yang-ext:mount/core-model-1-4:control-construct/logical-termination-point=<ltp-uuid>/name=externalLabel

headers:

• Accept: application/yang-data+json
• Content-Type: application/yang-data+json

body:

{
    "name": [
        {
            "value-name": "externalLabel",
            "value": "operator-given-name-for-ltp"
        }
    ]
}

Related Contribution in Email from 2020-04-30

Latest discussions revealed the following documented issues:

• https://github.com/openBackhaul/macInterface/issues/27 
• https://github.com/openBackhaul/macInterface/issues/28
• https://github.com/openBackhaul/macInterface/issues/29
• https://github.com/openBackhaul/macInterface/issues/30

→ all for issues on the agenda for decision next week 2020-07-29 - Please send comments to be addressed until 2020-07-27 - Thanks!

rxCollisions attributes to be added to WireInterfaceStatus and WireInterfacePerformanceType

• https://github.com/openBackhaul/wireInterface/issues/31
• https://github.com/openBackhaul/macInterface/issues/31

frame coutners

• RFC2819 - no history
• Proposal: Moving from history to statistics

https://github.com/openBackhaul/macInterface/issues/33

UML Model based on ONF CoreModel 1.4

• FD for VLANs → FD ↔ EthernetSwitsh
• FC for a single VLAN ID

VLAN Model with reduced scope. 

review period for documents from August 2019 will end 2020-06-09

• https://github.com/openBackhaul/vlanInterface/tree/tsp
• https://github.com/openBackhaul/vlanFd/tree/tsp
• https://github.com/openBackhaul/vlanFc/tree/tsp

Ongoing work...

How to align between Controller/Apps/Mediator/Devices?

Please see related email: https://groups.google.com/a/opennetworking.org/forum/#!topic/wireless-transport/daCPBnPKJzo

Feedback from vendors available => Vendors confirmed to be able to store an external equipment label and an external interface label on the device.

The following text has been added to the TransmitterEquipment document:

ControlConstruct and LogicalTerminationPoint

• While creating an instance of ControlConstruct or LogicalTerminationPoint, an instance of the NameAndValue datatype at the name attribute, which is inherited from the GlobalClass, shall be automatically created and filled with valueName:“externalLabel” and value: “”(empty String).
• After rebooting, the interface (e.g. mediator) the last configured value shall be represented again.

based on the proposal made in the issue:

Proposal:
The dropping-behavior-kind shall become part of a Profile,

• which can be instantiated multiple times, in case the device allows independently adjusting the dropping-behavior-kind per interface,
• or just a single time, in case the device allows adjusting the dropping-behavior-kind just on device/switch level.

further details should be agreed. 

1. A new profile type should be created, called "PROFILE_NAME_TYPE_DROPPING_PROFILE
2. The profile details are just extensible ENUM (yang: identity) similar like "dropping-behavior-kind-type"
3. ethernet-container-capability: available-dropping-behavior-kind-list will be of type "identity-ref" to the PROFILE_NAME_TYPE_DROPPING_PROFILE
4. ethernet-container-configuration: dropping-behavior-kind will be of type be of type "identity-ref" an entry in  ethernet-container-capability/available-dropping-behavior-kind-list
5. The pointers from ethernet-container-capability and ethernet-container-configuration allow the following use cases
   1. The EthernetSwitch (FD) allows only one Profile, all capabilities and all configuration are "static" because only one Profile exists. Any dynamic configuration happens in the Profile itself.
   2. Several Profiles with different configuration/behavior exists - ("static profiles"). Any configuration happens only by switching the profile.
   3. a combination of a) and b), which is not recommended due to unnecessary complexity.

Conclusion during the discussion:

• investigate in
  • adding another ethernet-container-capability attribute to express, if the LTP
    • can,
    • must,
    • must-not follow the configuration on device (forwarding-domain?) level
  • creating a device (forwarding-domain) PAC to uml:specify (yang:augment) ETH-Switch capabilities and configuration
• Further discussion on agenda for 2020-06-10.