This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
RE: getaddrinfo sort destination ip list
- From: "Wu, Zhao-Ming (Beijing, CMS)" <zwu at hpe dot com>
- To: libc-maintainers <libc-maintainers at gnu dot org>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Tue, 7 May 2019 02:55:01 +0000
- Subject: RE: getaddrinfo sort destination ip list
- References: <AT5PR8401MB0564C597BD555BE61DC238D6B0370@AT5PR8401MB0564.NAMPRD84.PROD.OUTLOOK.COM>
Hi,
I want to know if there is a plan for glibc to implement RFC6724? (The latest glibc2.29 still implement RFC3484 from my understanding)
Especially the "common prefix length" part. (since RFC3484 break DNS load balancing which we are using in our product. So I suppose DNS load balancing would be fine with RFC6724.
Thanks,
Zhaoming
RFC3484:
2.2 common Prefix Length
We define the common prefix length CommonPrefixLen(A,B) of two addresses A and B as the length of the longest prefix (looking at the most significant, or leftmost, bits) that the two addresses have in common. It ranges from 0 to 128.
RFC 6724:
Common Prefix Length
We define the common prefix length CommonPrefixLen(S,D) of a source address S and a destination address D as the length of the longest prefix (looking at the most significant, or leftmost, bits) that the two addresses have in common, up to the length of S's prefix (i.e., the portion of the address not including the interface ID). For example, CommonPrefixLen(fe80::1, fe80::2) is 64.