951 Encoding of Owner attribute

Created: 10 Dec 2012

Status: In Force (green)

Part: Part 8-1 (2011; Edition 2)

Links:

Page: 76

Clause: 17.1.2

Paragraph:

Category: Issue may impact interoperability of implementations of Edition 2

Issue

There is no clear description of encoding of IP address in V-Get response to Owner attribute in RCB: type (OctetString64) and possiblity of setting there IED Name of the client (as described in part 7-2) suggest textual encoding as for example
192.168.0.23 could be 3139322E3136382E302E3233
however MAC address in Addr structure in GCB is encoded on 6 bytes so for example
MAC 01-0C-CD-01-00-00 is encoded as 010CCD010000
This approach could imply encoding IP 192.168.0.23 as C0A80017

Proposal

Add Note 3 with example of encoding the value (preferably as in first example from above to be consistent with possible decoding of textual IED names).

Discussion	Created	Status
The UCA testing group agree with the C0A80017 encoding solution.	12 Dec 12	Discussion (red)
Encoding of IP address as octet string must be unique. Example of encoding as character string does not meet this need (it could as well be coded 3139322E3136382E3030302E303233). Suggest encoding IP4 addresses as exactly 4 octets as in C0A80017 (and IPv6 addresses as 16 octets if we accept IPv6)	12 Dec 12	Triage

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1