<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Fearghas explicitly identified:<br>
</p>
<blockquote>
<p>
<blockquote type="cite">
<pre wrap="">How does an IX that operates at Layer 2 drive the price of IPv4 up ?</pre>
</blockquote>
</p>
</blockquote>
While I've never seen a Layer2 only IX (presumably just an unmanaged
switch in a colo DC?).<br>
The specific question is quite succinct.<br>
<br>
Presumably Fearchas operates, participates in, or knows of such an
IX.<br>
<br>
<br>
-Tim<br>
<br>
<div class="moz-cite-prefix">On 14/09/16 12:27, Silvan M. Gebhardt
wrote:<br>
</div>
<blockquote
cite="mid:491888197.3089013.1473848838598.JavaMail.zimbra@openfactory.ch"
type="cite">
<pre wrap="">yes but the IX assigns the Peering IP's in their subnet Allocation ;)
so it would be "Price v4 and v6 peering ip's differently"
----- Ursprüngliche Mail -----
Von: "Tim Armstrong" <a class="moz-txt-link-rfc2396E" href="mailto:t.armstrong@nerdalize.com"><t.armstrong@nerdalize.com></a>
An: <a class="moz-txt-link-abbreviated" href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a>
Gesendet: Mittwoch, 14. September 2016 12:17:23
Betreff: Re: [members-discuss] Input from Membership on RIPE NCC Charging Scheme Model
You do understand Layer2 is MAC right? IP is in Layer3.
On 14/09/16 12:07, Paul Webb wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Sell IPv6 ports and IPv4 ports ?
-----Original Message-----
From: members-discuss [<a class="moz-txt-link-freetext" href="mailto:members-discuss-bounces@ripe.net">mailto:members-discuss-bounces@ripe.net</a>] On Behalf Of Fearghas Mckay
Sent: 14 September 2016 11:02
To: <a class="moz-txt-link-abbreviated" href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a>
Subject: Re: [members-discuss] Input from Membership on RIPE NCC Charging Scheme Model
Paul
</pre>
<blockquote type="cite">
<pre wrap="">On 14 Sep 2016, at 10:40, Paul Webb <a class="moz-txt-link-rfc2396E" href="mailto:Paul.Webb@clearstreamgroup.co.uk"><Paul.Webb@clearstreamgroup.co.uk></a> wrote:
Certainly RIPE, but organisations such as the IX's, could also start making IPv4 more expensive and help the migration and I'd argue they should be. Sadly the larger LIR's have a disproportionate influence in all the important places, which doesn't help.
</pre>
</blockquote>
<pre wrap="">How does an IX that operates at Layer 2 drive the price of IPv4 up ?
Chris
</pre>
<blockquote type="cite">
<pre wrap="">If you look at the UK for example, I can't think of any large LIR/ISP that is fully IPv6 ready (there's only one I can think of that isn't too far off), yet I can think of many smaller ones that are 100% good to go and have been for some time.
</pre>
</blockquote>
<pre wrap="">Apart from BT and Sky that have both just finished the v6 rollouts.
f
----
If you don't want to receive emails from the RIPE NCC members-discuss mailing list, please log in to your LIR Portal account and go to the general page:
<a class="moz-txt-link-freetext" href="https://lirportal.ripe.net/general/">https://lirportal.ripe.net/general/</a>
Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses.
----
If you don't want to receive emails from the RIPE NCC members-discuss
mailing list, please log in to your LIR Portal account and go to the general page:
<a class="moz-txt-link-freetext" href="https://lirportal.ripe.net/general/">https://lirportal.ripe.net/general/</a>
Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses.
</pre>
</blockquote>
<pre wrap="">
----
If you don't want to receive emails from the RIPE NCC members-discuss
mailing list, please log in to your LIR Portal account and go to the general page:
<a class="moz-txt-link-freetext" href="https://lirportal.ripe.net/general/">https://lirportal.ripe.net/general/</a>
Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses.
</pre>
</blockquote>
<br>
</body>
</html>