]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> AW: [IRCServices] ircservices and support for/of IPv6 | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=AW%3A%20%5BIRCServices%5D%20ircservices%20and%20support%20for/of%20IPv6&In-Reply-To="> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="003674.html"> | |
11 | <LINK REL="Next" HREF="003676.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>AW: [IRCServices] ircservices and support for/of IPv6</H1> | |
15 | <B>Ian R. Justman</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=AW%3A%20%5BIRCServices%5D%20ircservices%20and%20support%20for/of%20IPv6&In-Reply-To=" | |
17 | TITLE="AW: [IRCServices] ircservices and support for/of IPv6">ianj at esper.net | |
18 | </A><BR> | |
19 | <I>Tue Mar 11 09:49:50 PST 2003</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="003674.html">AW: [IRCServices] ircservices and support for/of IPv6 | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="003676.html">AW: AW: [IRCServices] ircservices and support for/of IPv6 | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#3675">[ date ]</a> | |
27 | <a href="thread.html#3675">[ thread ]</a> | |
28 | <a href="subject.html#3675">[ subject ]</a> | |
29 | <a href="author.html#3675">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE> | |
35 | ||
36 | Yusuf Iskenderoglu wrote: | |
37 | ><i> The answer to this question is simple. | |
38 | </I>><i> Services could have had used char arrays of fixed sizes to store | |
39 | </I>><i> hostnames, which could be too small for ipv6 addresses. | |
40 | </I>><i> | |
41 | </I>><i> Look at the definition of HOSTIPLEN in several ircds, those, | |
42 | </I>><i> which support IPv6 have HOSTIPLEn=53, those who do not have it set | |
43 | </I>><i> to 15. | |
44 | </I> | |
45 | I'm going to move what I wrote in my previous e-mail here: | |
46 | ||
47 | >>Mainly because Services does not do any DNS resolution (would | |
48 | >>slow Services | |
49 | >>down something fierce; that's what the server's for), the address, | |
50 | >>regardless of type (name vs. IP) or IPv#, is always going to | |
51 | >>be a text field. | |
52 | ||
53 | Remember, Services already has enough on its plate where DNS will only | |
54 | add to the burden. that's why the server does its DNS lookup. | |
55 | ||
56 | The only time Services ever needs to give a damn about IPv6 is when it's | |
57 | connecting to its next-hop server. :) | |
58 | ||
59 | --Ian R. Justman, Co-Founder and Postmaster, The EsperNet IRC Network. | |
60 | ||
61 | ----- | |
62 | Ian R. Justman <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ianj at esper.net</A> (Official | |
63 | EsperNet business) | |
64 | Co-Founder and Postmaster, The EsperNet IRC Network | |
65 | Server Administrator, chocobo.esper.net "IJ" on IRC | |
66 | ||
67 | PGP/GPG keys available upon request, or from any PGP keyserver. | |
68 | ||
69 | </PRE> | |
70 | ||
71 | <!--endarticle--> | |
72 | <HR> | |
73 | <P><UL> | |
74 | <!--threads--> | |
75 | <LI>Previous message: <A HREF="003674.html">AW: [IRCServices] ircservices and support for/of IPv6 | |
76 | </A></li> | |
77 | <LI>Next message: <A HREF="003676.html">AW: AW: [IRCServices] ircservices and support for/of IPv6 | |
78 | </A></li> | |
79 | <LI> <B>Messages sorted by:</B> | |
80 | <a href="date.html#3675">[ date ]</a> | |
81 | <a href="thread.html#3675">[ thread ]</a> | |
82 | <a href="subject.html#3675">[ subject ]</a> | |
83 | <a href="author.html#3675">[ author ]</a> | |
84 | </LI> | |
85 | </UL> | |
86 | ||
87 | </body></html> |