<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How can the engineering community and the users meet ?</title>
	<atom:link href="http://patrick.vande-walle.eu/internet/how-can-the-engineering-community-and-the-users-meet/feed/" rel="self" type="application/rss+xml" />
	<link>http://patrick.vande-walle.eu/internet/how-can-the-engineering-community-and-the-users-meet/</link>
	<description>Random thoughts about the Internet and life</description>
	<lastBuildDate>Sat, 21 Aug 2010 15:23:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Leo</title>
		<link>http://patrick.vande-walle.eu/internet/how-can-the-engineering-community-and-the-users-meet/comment-page-1/#comment-18641</link>
		<dc:creator>Leo</dc:creator>
		<pubDate>Fri, 21 Sep 2007 09:27:41 +0000</pubDate>
		<guid isPermaLink="false">http://patrick.vande-walle.eu/internet/how-can-the-engineering-community-and-the-users-meet/#comment-18641</guid>
		<description>Patrick,

No-one has argued in favour of assigning just a /64 to an ordinary domestic connection. In fact, no-one is suggesting that ISPs should not be able to assign a /48 to a domestic connection, either. 

The proposal you are presumably talking about suggests using a /56 as the unit for measuring how full an ISP&#039;s allocation is. The issue the is being debated -- and yes this is mostly by ISPs -- is how much pain an ISP should bear before it can get more space. Should an ISP be required to pack more assignments into its allocation or should it have more breathing room and be able to put more hierarchy into its network?

If end users want to take part in discussions then they are welcome to do so. But there haven\&#039;t been any proposals to cause extra pain to domestic Internet users yet.</description>
		<content:encoded><![CDATA[<p>Patrick,</p>
<p>No-one has argued in favour of assigning just a /64 to an ordinary domestic connection. In fact, no-one is suggesting that ISPs should not be able to assign a /48 to a domestic connection, either. </p>
<p>The proposal you are presumably talking about suggests using a /56 as the unit for measuring how full an ISP&#8217;s allocation is. The issue the is being debated &#8212; and yes this is mostly by ISPs &#8212; is how much pain an ISP should bear before it can get more space. Should an ISP be required to pack more assignments into its allocation or should it have more breathing room and be able to put more hierarchy into its network?</p>
<p>If end users want to take part in discussions then they are welcome to do so. But there haven\&#8217;t been any proposals to cause extra pain to domestic Internet users yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Vande Walle</title>
		<link>http://patrick.vande-walle.eu/internet/how-can-the-engineering-community-and-the-users-meet/comment-page-1/#comment-18638</link>
		<dc:creator>Patrick Vande Walle</dc:creator>
		<pubDate>Fri, 21 Sep 2007 08:46:09 +0000</pubDate>
		<guid isPermaLink="false">http://patrick.vande-walle.eu/internet/how-can-the-engineering-community-and-the-users-meet/#comment-18638</guid>
		<description>Leo,

To be more specific, the reference to the IPv6 prefix is connected to a recent discussion that popped up on the &lt;a href=&quot;http://www.ripe.net/ripe/maillists/archives/address-policy-wg/2007/msg00595.html&quot;&gt;Ripe Address policy&lt;/a&gt; list. 

To summarize, there might be a need in a few years from now to have several subnets on a home network. Thus, an ISP should allocate more than a /64 to CPEs, because one cannot subnet a /64. 

&lt;a href=&quot;http://tools.ietf.org/rfc/rfc3177.txt&quot;&gt;RFC3177&lt;/a&gt; recommends a /48 for &lt;b&gt;home&lt;/b&gt; sites, but it is not the  path RIRs have followed since. Agree, /48 may be overkill and certainly a /56 would be enough for home sites. This is a discussion we should have. Which forum holds that discussion is not really important as such, as long as the results are effectively implemented. 

This may have consequences further down on the IP address allocations to ISPs. From an industrial point of view, the Linksys, D-Link and other home CPE manufacturers should be made aware their boxes may need to support subnetting in IPv6. Given these boxes can have a rather long lifetime, it may be worth planning ahead.</description>
		<content:encoded><![CDATA[<p>Leo,</p>
<p>To be more specific, the reference to the IPv6 prefix is connected to a recent discussion that popped up on the <a href="http://www.ripe.net/ripe/maillists/archives/address-policy-wg/2007/msg00595.html">Ripe Address policy</a> list. </p>
<p>To summarize, there might be a need in a few years from now to have several subnets on a home network. Thus, an ISP should allocate more than a /64 to CPEs, because one cannot subnet a /64. </p>
<p><a href="http://tools.ietf.org/rfc/rfc3177.txt">RFC3177</a> recommends a /48 for <b>home</b> sites, but it is not the  path RIRs have followed since. Agree, /48 may be overkill and certainly a /56 would be enough for home sites. This is a discussion we should have. Which forum holds that discussion is not really important as such, as long as the results are effectively implemented. </p>
<p>This may have consequences further down on the IP address allocations to ISPs. From an industrial point of view, the Linksys, D-Link and other home CPE manufacturers should be made aware their boxes may need to support subnetting in IPv6. Given these boxes can have a rather long lifetime, it may be worth planning ahead.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leo</title>
		<link>http://patrick.vande-walle.eu/internet/how-can-the-engineering-community-and-the-users-meet/comment-page-1/#comment-18635</link>
		<dc:creator>Leo</dc:creator>
		<pubDate>Thu, 20 Sep 2007 21:41:04 +0000</pubDate>
		<guid isPermaLink="false">http://patrick.vande-walle.eu/internet/how-can-the-engineering-community-and-the-users-meet/#comment-18635</guid>
		<description>Why do you say that &quot;which IPv6 prefix is going to be allocated by your ISP to your home network in a few years from now is an important one&quot;? Why should it make any difference to me which of the billions of network prefixes is assigned to me? Do you know about a special group of prefixes that work better than the rest?</description>
		<content:encoded><![CDATA[<p>Why do you say that &#8220;which IPv6 prefix is going to be allocated by your ISP to your home network in a few years from now is an important one&#8221;? Why should it make any difference to me which of the billions of network prefixes is assigned to me? Do you know about a special group of prefixes that work better than the rest?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stéphane Bortzmeyer</title>
		<link>http://patrick.vande-walle.eu/internet/how-can-the-engineering-community-and-the-users-meet/comment-page-1/#comment-18631</link>
		<dc:creator>Stéphane Bortzmeyer</dc:creator>
		<pubDate>Thu, 20 Sep 2007 06:39:10 +0000</pubDate>
		<guid isPermaLink="false">http://patrick.vande-walle.eu/internet/how-can-the-engineering-community-and-the-users-meet/#comment-18631</guid>
		<description>Interesting article, but I have a small fix to make. The EAI working group, which works on Internationalized Email Addresses have been founded in March 2006, 18 months ago (http://www1.ietf.org/mail-archive/web/ima/current/msg00178.html). And, as often with the IETF, the actual work started even before.

True, it should have been done earlier, true, the work pace is too slow, but there is something going one, the happy volunteers do work.</description>
		<content:encoded><![CDATA[<p>Interesting article, but I have a small fix to make. The EAI working group, which works on Internationalized Email Addresses have been founded in March 2006, 18 months ago (<a href="http://www1.ietf.org/mail-archive/web/ima/current/msg00178.html" rel="nofollow">http://www1.ietf.org/mail-archive/web/ima/current/msg00178.html</a>). And, as often with the IETF, the actual work started even before.</p>
<p>True, it should have been done earlier, true, the work pace is too slow, but there is something going one, the happy volunteers do work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
