1208 IPv6 Address format
Created: 23 Jan 2014
Status: In Force (green)
Part: Part 6 (2009-12; Edition 2)
Category: Issue may impact interoperability of implementations of Edition 2
The IPv6 address formats should be represented and parsed as "lower case hexadecimal" The uppercase hex is not anymore allowed.
Short formats should be allowed:
(Caveat: the IP address format does not allow for their transmission
since it is fixed to 16 octets in 90-5).
IPv6-mapped to IPv4 should be considered, since a common mapping from the current IPv4 to IPv6 addresses is foreseen.
192.0.2.1 -> 64:ff9b::192.0.2.1
Use only IPv6 formats allowed by IETF.
Check the composition rules for the patterns in SCL,
see final proposal
||05 Aug 14
||In Force (green)
The final Proposal is:
type IP, IP-SUBNET, IP-GATEWAY are only for IPv4 address scheme.
type IP-SUBNET is therefore for IPv4 only, and only allows the x.y.z.w notation as it always did.
New types are addeed for IPv6, IPv6-GATEWAY, IPv6-SUBNET.
IPv6 - for IPv6 address - full length mandatory.
IPv6-SUBNET - for IPv6 subnets - /x notation
IPv6-GATEWAY - for IPv6 address - full length mandatory
|16 Jul 14
IPv6 adresses shall always be complete using small characters. Additionally the IP V6 Subnet notation with slash shall be used for IP V6 addresses in the parameter IP-SUBNET.
||26 Jun 14
We should not be changing the representation of IPv4 information (address or subnet). This would create backward compatibility issues and should not be done.
||04 Jun 14
The main goal of IEC 61850 is long term interoperability, with SCL especially of tools. Therefore IPv6 adresses shall always be complete using small characters. An adaption according to results from AHG8 e.g. concerning IPv4 mapping could follow later.
||27 Feb 14
There is a difference between what tools display / editors allow, and what is written in a SCL file. Having the complete string make the format interoperable for every implementation. Allowing short format in SCL forces to change the current restricted version of the format.
I do not recommend to change, and would prefer to postpone the responsability to HMIs to display a short format.
|10 Feb 14
Privacy | Contact | Disclaimer
Tissue DB v. 126.96.36.199