View Issue Details

IDProjectCategoryView StatusLast Update
000887910000-006: MappingsSpecpublic2023-06-21 14:40
ReporterJim Luth Assigned ToRandy Armstrong  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionreopened 
Product Version1.05.01 
Fixed in Version1.05.03 RC1 
Summary0008879: Missing conformance units and spec language for DNS resolution
Description

As discussed in 2023-02-14 UA WG call, the UAFX WG has requirements for controllers to support host name resolution via DNS. Ideally, the UAFX spec would be able to point to content and profiles in the UA spec, since this is capability not specific to UAFX.

It was agreed that the best solution would be to have CUs/facets for DNS client capability, along with some clarifications in Parts 4/5/6 (for client/server) as needed and Part 14 for PubSub

See the attached powerpoint for more detailed information.

TagsNo tags attached.
Attached Files
Commit Version1.05.03 RC
Fix Due Date

Relationships

related to 0008700 closedKarl Deiretsbacher 10000-007: Profiles Missing conformance units and spec language for DNS resolution 
related to 0008877 closedMatthias Damm 10000-004: Services Missing conformance units and spec language for DNS resolution 
related to 0008880 closedMatthias Damm 10000-014: PubSub Missing conformance units and spec language for DNS resolution 

Activities

Jim Luth

2023-04-18 18:40

administrator   ~0019207

I suggest we create 3 separate Facets to indicate support of DNS resolution via:

  • host file
  • mDNS
  • DNS

Jim Luth

2023-04-18 18:40

administrator   ~0019208

Cloning to all Parts likely to be affected.

Randy Armstrong

2023-05-12 04:38

administrator   ~0019330

Added text:

Connections may be initiated by the Client or by the Server when they create a TransportConnection and establish a communication with their peer. The connection is initiated by using an EndpointUrl that specifies a network address where a peer listens for new connections. The EndpointUrl specifies an network address that is accessible to the initiator. If the listener is behind a NAT firewall, the EndpointUrl specifies an address outside the firewall. If the EndpointUrl specifies a domain name then the initiator requires access to a domain name resolution service (e.g., the DNS protocol) that maps the domain name onto a useable network address.

Jim Luth

2023-05-16 15:45

administrator   ~0019383

Agreed to changes in Web Meeting.

Jim Luth

2023-06-20 19:20

administrator   ~0019581

Needs more updates based on today's meeting.

Jim Luth

2023-06-21 13:42

administrator   ~0019592

Agreed to changes edited in Virtual F2F.

Issue History

Date Modified Username Field Change
2023-04-18 18:40 Jim Luth New Issue
2023-04-18 18:40 Jim Luth Status new => assigned
2023-04-18 18:40 Jim Luth Assigned To => Randy Armstrong
2023-04-18 18:40 Jim Luth Issue generated from: 0008700
2023-04-18 18:40 Jim Luth Note Added: 0019207
2023-04-18 18:40 Jim Luth Note Added: 0019208
2023-04-18 18:40 Jim Luth Relationship added related to 0008700
2023-04-18 18:40 Jim Luth Project 10000-007: Profiles => 10000-006: Mappings
2023-05-12 04:38 Randy Armstrong Status assigned => resolved
2023-05-12 04:38 Randy Armstrong Resolution open => fixed
2023-05-12 04:38 Randy Armstrong Note Added: 0019330
2023-05-16 15:45 Jim Luth Status resolved => closed
2023-05-16 15:45 Jim Luth Fixed in Version => 1.05.03 RC1
2023-05-16 15:45 Jim Luth Note Added: 0019383
2023-06-20 19:20 Jim Luth Status closed => feedback
2023-06-20 19:20 Jim Luth Resolution fixed => reopened
2023-06-20 19:20 Jim Luth Note Added: 0019581
2023-06-20 19:20 Jim Luth Status feedback => assigned
2023-06-21 13:42 Jim Luth Status assigned => closed
2023-06-21 13:42 Jim Luth Commit Version => 1.05.03 RC
2023-06-21 13:42 Jim Luth Note Added: 0019592
2023-06-21 13:43 Matthias Damm Relationship added related to 0008877
2023-06-21 13:47 Matthias Damm Relationship added related to 0008880