[TSDR-72] TSC Issues that do or do not effect TSDR Created: 18/Jul/18 Updated: 25/Jul/18 |
|
| Status: | Open |
| Project: | tsdr |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Medium |
| Reporter: | Scott Melton | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
In order to avoid redundant analysis, this documents TSC issues that do or do not effect TSDR. As these TSC issues arise, e.g. upstream version bumps, framework changes, upstream dependency changes, please document them here with a brief description of why they do not effect TSDR or a link to a TSDR issue that was created to support the TSC change for issues that do effect TSDR. |
| Comments |
| Comment by Scott Melton [ 18/Jul/18 ] |
|
Does not effect TSDR.
TSC-125 opendaylight-inventory is to be replaced with an ietf-network instance - TSDR does not use ietf-network directly. TSC-124 RFC8345 defines ietf-network(-topology) - TSDR does not use ietf-network-topology directly. TSC-123 Adopt NMDA-compatible versions of ietf-interfaces and ietf-ip - TSDR does not use ietf-interfaces or ietf-ip directly. |
| Comment by Scott Melton [ 25/Jul/18 ] |
|
Effects Types.Char_ARRAY, TypeUnion, not used in TSDR. |