From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Tom Dunstan <pgsql(at)tomd(dot)cc>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: IPv6 link-local addresses and init data type |
Date: | 2016-05-31 10:40:03 |
Message-ID: | 574D6A03.8040607@proxel.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 05/31/2016 04:06 AM, Tom Lane wrote:
> Andreas Karlsson <andreas(at)proxel(dot)se> writes:
>> On 05/31/2016 02:37 AM, Haribabu Kommi wrote:
>>> The % delimiter character is not only used at the end of the IPV6 address,
>>> from the RFC document, it is possible as follows also.
>>>
>>> fe80::%2/64
>>>
>>> we need to handle both the scenarios, it may not be a straight
>>> forward to store the zone id data.
>
>> This case needs to be handled by the parser for at least the cidr type,
>> but I do not think it would make parsing any trickier.
>
> Unless there's a semantic difference between fe80::1%2/64 and
> fe80::1/64%2, this doesn't seem like a big deal to me.
As far as I can till only fe80::1%2/64 is valid, but I am not 100% sure.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Karlsson | 2016-05-31 10:47:15 | Re: Binary I/O for isn extension |
Previous Message | Marco Atzeri | 2016-05-31 10:26:21 | Re: Question and suggestion about application binary compatibility policy |