View Issue Details

IDProjectCategoryView StatusLast Update
0009107Part 84: UAFX ProfilesSpecpublic2024-12-18 15:16
ReporterBob Lattimer Assigned ToBob Lattimer  
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionreopened 
Product Version1.00.00 
Target Version1.00.03Fixed in Version1.00.02 
Summary0009107: DNS for host name resolution and mDNS for responder support need to be added to the UAFX Controller Profile.
Description

Part 82 has added requirements for DNS and mDNS to satisfy marketing requirements for host name resolution and device discovery without a central server. The UACore 1.05 Host Resolution Facet requires DNS, and the UACore 1.05 Subnet Discovery Server Facet require mDNS responder support. Both of these Facets will ultimately be added to a Networking Profile (most likely the UAFX Station Facet), but until the C2D releases, because these are breaking Profile changes, these Facets will be added to the UAFX Controller Profile in order to minimize the impact of the change on other Profiles.

TagsNo tags attached.

Relationships

related to 0009106 closedBob Lattimer Part 82: UAFX Networking mDNS responder support needs to be added to Part 82 

Activities

Bob Lattimer

2023-08-16 22:04

manager   ~0019893

Last edited: 2023-09-19 22:38

The UACore 1.05 Host Resolution Facet requiring DNS and the UACore 1.05 Subnet Discovery Server Facet optionally requiring mDNS were added to the UAFX Controller 2023 Profile.

Greg Majcher

2023-09-20 14:21

manager   ~0020035

The changes were reviewed and approved in an AWG meeting.

Bob Lattimer

2023-10-06 14:38

manager   ~0020102

The UACore 1.05 Host Resolution Facet requiring DNS and the UACore 1.05 Subnet Discovery Server Facet were moved to the new UAFX Controller Server 2023 Profile, and the new server Profile replaces the old server Profile in the UAFX Controller 2023 Profile. This results in the exact same change in required CUs but places these two Facets in a more correct place.

Paul Hunkar

2024-12-06 08:51

manager   ~0022188

the support for DNS resolution applies to the ConnectionManager and should have been applied to the CM profile , not the controller server profile. The mDNS registration does apply to the controller.

Greg Majcher

2024-12-18 15:16

manager   ~0022230

Name resolution needs to appear in both the controller and CM profiles. Update the CM profile to include the UACore 1.05 Host Resolution Facet requiring DNS and the UACore 1.05 Subnet Discovery Server Facets.

Issue History

Date Modified Username Field Change
2023-08-16 22:01 Bob Lattimer New Issue
2023-08-16 22:01 Bob Lattimer Status new => assigned
2023-08-16 22:01 Bob Lattimer Assigned To => Bob Lattimer
2023-08-16 22:04 Bob Lattimer Status assigned => resolved
2023-08-16 22:04 Bob Lattimer Resolution open => fixed
2023-08-16 22:04 Bob Lattimer Fixed in Version => 1.00.01
2023-08-16 22:04 Bob Lattimer Note Added: 0019893
2023-08-16 22:05 Bob Lattimer Relationship added related to 0009106
2023-09-19 22:38 Bob Lattimer Note Edited: 0019893
2023-09-20 14:21 Greg Majcher Status resolved => closed
2023-09-20 14:21 Greg Majcher Note Added: 0020035
2023-09-26 21:45 Bob Lattimer Fixed in Version 1.00.01 => 1.00.02
2023-10-06 14:38 Bob Lattimer Note Added: 0020102
2024-12-06 08:51 Paul Hunkar Status closed => feedback
2024-12-06 08:51 Paul Hunkar Resolution fixed => reopened
2024-12-06 08:51 Paul Hunkar Note Added: 0022188
2024-12-06 08:51 Paul Hunkar Status feedback => assigned
2024-12-18 14:57 Greg Majcher Target Version => 1.00.03
2024-12-18 15:16 Greg Majcher Note Added: 0022230