Requested revision
Standard: | IEEE Std 802.1Qcc-2018 | Clause: | 46.3 |
Clause title: | YANG data module definitions for TSN user/network |
Rationale for revision
A comment on P802.1Qdj was suggested to be a Maintenance item. Comment: Comment Type TR PDF Page 16 Stream ID is a String Regex MAC plus a Unique ID. That means that as far as this YANG goes AA-BB-CC-DD-EE-FF:00-01 is different than aa-bb-cc-ee-ff:00-01 even though they are the same stream ID. SuggestedRemedy This was pointed out in YANGsters as a case to avoid. The issue is that an administrator could inadvertently create multi instances for basically the same stream ID that would have to be resolved because eventually something converts the stream-id into a normalized type. One solution is to force lowercase or uppercase for stream ID so there is no ambiguity ever. I think this is the best solution and probably how we should have handled the MAC address formatting issue. Response The current form of StreamID is defined in the ieee802-dot1q-tsn-types YANG module defined in IEEE Std 802.1Qcc-2018 and has just been pulled into the YANG module in IEEE P802.1Qdj. Please submit a maintenance request to address this issue.
Proposed text
There are two possible revisions: 1) Force the regex to be case sensitive and there will be no issue. e.g. pattern '[0-9A-F]{2}(-[0-9A-F]{2}){5}:[0-9A-F]{2}-[0-9A-F]{2}'; 2) Document the issue. If a user enters two Stream ID that are the same the commit of data will most likely fail with duplicate. The suggested text would be to use one case format only. (Either all uppercase for A-F or all lowercase a-f.)
Impact on existing networks
This is really only an input error while entering into the schema.
Most systems would raise a duplicate Error as soon as data is committed.
The case sensitivity is only because this is used as a key by other
modules which may happen before a commit. There is no impact once data
has been successfully committed because The software that accepts the
Stream ID would have normalized the Format.
Originator
Name: | Don Fedyk | Email: | dfedyk@labn.net |
Affiliation: | LabN Consulting L.L.C. | ||
Submitted: | 2021-02-22 |