Re: What is Native IPv6
JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Sat, 30 July 2011 09:45 UTC
Return-Path: <prvs=119257c7bb=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56D0921F8A51 for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 02:45:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.462
X-Spam-Level:
X-Spam-Status: No, score=-104.462 tagged_above=-999 required=5 tests=[AWL=-2.137, BAYES_00=-2.599, DATE_IN_FUTURE_03_06=0.274, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vbxHDnujvRsb for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 02:45:51 -0700 (PDT)
Received: from consulintel.es (gr2000.consulintel.es [213.172.48.138]) by ietfa.amsl.com (Postfix) with ESMTP id BB33A21F886E for <ietf@ietf.org>; Sat, 30 Jul 2011 02:45:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1312018642; x=1312623442; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding: Reply-To; bh=DyVUbKUxYrxNBsYD5SY9FYGvb7HICZVf4yMEgvpdcZM=; b=nKN GE46aubmml8mz8+TTcvfqxJRtGriouqKZ2RBuRqOqVfm9aKwuWeXY4V0U43TN8wy v9W8DoSXdx33Tms6F8V1SyjaZlLaw9CGjRILINoQoZb7QG97nVIwHMW+FXoseZ3i SNppZv0sRrsLvxb9OGW+l4GXs41nFW/fizLMixoI=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=qsdYmGYF9QwdGocJ6TWOjaxDmqtd56P0uT+iaKOuZvoLobb1dh4fIIDhTRdX bEn6GZO4DvW/MRWcjZTsD9a4OAhJaD1iYx4TK7Nxtt05Y02tp2xpvOMDe w8Z38nB/onT+wPGOr4jch8eusLJnz6eTqk8Gzb1DjZ0SnbPihdl9UQ=;
X-MDAV-Processed: consulintel.es, Sat, 30 Jul 2011 11:37:22 +0200
Received: from [10.1.0.16] by consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50003954828.msg for <ietf@ietf.org>; Sat, 30 Jul 2011 11:37:22 +0200
X-Spam-Processed: consulintel.es, Sat, 30 Jul 2011 11:37:22 +0200 (not processed: message from trusted or authenticated source)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:110730:md50003954828::qaoYVmsfQ1FvnDQc:00005Wwd
X-MDRemoteIP: 94.175.239.226
X-Return-Path: prvs=119257c7bb=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/14.12.0.110505
Date: Sat, 30 Jul 2011 10:45:27 -0400
Subject: Re: What is Native IPv6
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF Discussion <ietf@ietf.org>
Message-ID: <CA599052.495A5%jordi.palet@consulintel.es>
Thread-Topic: What is Native IPv6
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF63B@newserver.arneill-py.local>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jul 2011 09:45:52 -0000
However, for what it matters here, 6rd is native after exiting from the ISP, same as 6to4 is native after exiting from the 6to4 relay. As we may not be able to know how "much" of the "native" IPv6 traffic is 6rd in the last mile, I think we should consider all 6rd traffic as native for those measurements, otherwise, we will be biasing the data. Even it may be the case of an ISP using 6rd for some part of its network, and native for the other. We may need to state "IPv6 native as measured, may be encapsulated in the last mile". Regards, Jordi -----Mensaje original----- De: Michel Py <michel@arneill-py.sacramento.ca.us> Responder a: <michel@arneill-py.sacramento.ca.us> Fecha: Fri, 29 Jul 2011 19:31:13 -0700 Para: Ole Troan <otroan@employees.org> CC: Tim Chown <tjc@ecs.soton.ac.uk>, IETF Discussion <ietf@ietf.org> Asunto: What is Native IPv6 >Ole, > >> Ole Troan wrote: >> I presume you are arguing that MPLS (6PE) is not native either? > >That's a tough one. > >What would make me say it is native is: MPLS is a L2/switching animal, >not a L3/routing one. In theory you can bind any L3 protocol such as >IPv4, IPv6, IPX, Appletalk, etc to it. So the MPLS interface is very >similar in some aspects to a real physical interface such as Ethernet or >HSSI. It reminds me of a frame-relay sub-interface in a past life. > >What would make me say it is not native is: you can't remove IPv4 out of >the equation. Frame relay does not even know about which L3 protocols it >transports, while MPLS is kinda going the reverse way in the stack: it >uses L3 packets/datagrams to encapsulate and transport "L2 frames". > > >Here's my take: >- You can have native IPv6 over Ethernet or HDLC or Sonet or any other >L2 technology. > >- Saying you have native IPv6 over fiber or copper is incorrect; you >have native IPv6 over GigE over {singlemode|multimode} (*) fiber or you >have IPv6 over Ethernet over GigE over (*) copper (or other examples) >(*) insert the appropriate 802.x standard > >- I like the idea of being native requiring the IPv6 to be bound to a L2 >interface. The gray area with 6PE is that the interface is logical, not >physical. > >- Native IPv6 over a 6to4 or a 6RD or any kind of L3-L3 tunnel is an >oxymoron. > > > >In other words: native IPv6 means: >a) IPv6 has to be bound to a L2 interface. >b) That interface can NOT be a tunnel interface using another L3 >protocol such as IPv4. > >Up for grabs: > >- c1) Is it acceptable to have a structural requirement to use IPv4 >(which would mean 6PE is native) or c2) is it a requirement that the >entire infrastructure (in the case of 6RD, the ISP's infrastructure) >supports IPv6 (which would mean that 6PE is not native). > >Food for thought: > >- If c2) is chosen, I would consider rephrasing a) so it becomes "IPv6 >has to be bound to a PHYSICAL L2 interface". Rationale: besides 6PE, are >there any other gray area candidates? > >- If one is in the business of writing an draft about "what is native >IPv6", and if one of the draft's goals is to reach -cough- consensus >-cough-, one may consider "forgetting" the 6PE classification >altogether. The one part that is not open for grabs with me is >classifying 6RD as native. > > >Michel. > >_______________________________________________ >Ietf mailing list >Ietf@ietf.org >https://www.ietf.org/mailman/listinfo/ietf ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) SM
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Douglas Otis
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Mykyta Yevstifeyev
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Noel Chiappa
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Roger Jørgensen
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Philip Homburg
- draft-ietf-v6ops-6to4-to-historic (yet again) Ronald Bonica
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Keith Moore
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Michael Richardson
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Ole Troan
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Michel Py
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Brian E Carpenter
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Noel Chiappa
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) John Leslie
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Martin Rex
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Christian Huitema
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Mark Andrews
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Cameron Byrne
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Ted Faber
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Brian E Carpenter
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Michel Py
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Randy Presuhn
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Mykyta Yevstifeyev
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Ronald Bonica
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Tim Chown
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Lorenzo Colitti
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Tim Chown
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Geoff Huston
- Re: 6to4v2 (as in ripv2)? (was: draft-ietf-v6ops-… Alexandru Petrescu
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) t.petch
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Joel Jaeggli
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Mikael Abrahamsson
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Ronald Bonica
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Templin, Fred L
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) james woodyatt
- Re: 6to4v2 (as in ripv2)? Brian E Carpenter
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Brian E Carpenter
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Randy Bush
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) GT RAMIREZ, Medel G.
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Sabahattin Gucukoglu
- Re: 6to4v2 (as in ripv2)? Masataka Ohta
- Re: 6to4v2 (as in ripv2)? Mark Andrews
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) George Michaelson
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Rémi Després
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) t.petch
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Rémi Després
- Re: 6to4v2 (as in ripv2)? Fred Baker
- Re: 6to4v2 (as in ripv2)? Keith Moore
- Re: [v6ops] 6to4v2 (as in ripv2)? Keith Moore
- Re: [v6ops] 6to4v2 (as in ripv2)? Cameron Byrne
- Re: [v6ops] 6to4v2 (as in ripv2)? Cameron Byrne
- Re: [v6ops] 6to4v2 (as in ripv2)? Mark Andrews
- Re: [v6ops] 6to4v2 (as in ripv2)? Mark Andrews
- Re: [v6ops] 6to4v2 (as in ripv2)? Cameron Byrne
- Re: [v6ops] 6to4v2 (as in ripv2)? Joel Jaeggli
- RE: 6to4v2 (as in ripv2)? Michel Py
- Re: RE: 6to4v2 (as in ripv2)? Cameron Byrne
- Re: [v6ops] 6to4v2 (as in ripv2)? Tim Chown
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Tore Anderson
- Re: [v6ops] 6to4v2 (as in ripv2)? Philip Homburg
- Re: "6to4 damages the Internet" (was Re: draft-ie… Keith Moore
- Re: [v6ops] 6to4v2 (as in ripv2)? Mark Townsley
- Re: [v6ops] 6to4v2 (as in ripv2)? John Mann (ITS)
- Re: [v6ops] 6to4v2 (as in ripv2)? Ted Lemon
- Re: [v6ops] 6to4v2 (as in ripv2)? Erik Kline
- Re: [v6ops] 6to4v2 (as in ripv2)? Mark Andrews
- Re: [v6ops] 6to4v2 (as in ripv2)? Douglas Otis
- Re: [v6ops] 6to4v2 (as in ripv2)? Mark Andrews
- Re: [v6ops] 6to4v2 (as in ripv2)? Thomas Nadeau
- Re: [v6ops] 6to4v2 (as in ripv2)? Tim Chown
- "6to4 damages the Internet" (was Re: draft-ietf-v… Keith Moore
- Re: [v6ops] 6to4v2 (as in ripv2)? Keith Moore
- Re: [v6ops] 6to4v2 (as in ripv2)? Keith Moore
- Re: [v6ops] 6to4v2 (as in ripv2)? Keith Moore
- Re: "6to4 damages the Internet" (was Re: draft-ie… Masataka Ohta
- Re: "6to4 damages the Internet" (was Re: draft-ie… Michael Richardson
- Re: "6to4 damages the Internet" (was Re: draft-ie… Lorenzo Colitti
- Re: [v6ops] 6to4v2 (as in ripv2)? Roger Jørgensen
- Re: [v6ops] 6to4v2 (as in ripv2)? Alexandru Petrescu
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Warren Kumari
- Re: "6to4 damages the Internet" (was Re: draft-ie… Masataka Ohta
- Re: [v6ops] 6to4v2 (as in ripv2)? Michael Richardson
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Alexandru Petrescu
- Re: [v6ops] 6to4v2 (as in ripv2)? Mark Andrews
- Re: "6to4 damages the Internet" (was Re: draft-ie… Philip Homburg
- Re: [v6ops] 6to4v2 (as in ripv2)? james woodyatt
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Michael Richardson
- IPv6 traffic distribution Michel Py
- Re: "6to4 damages the Internet" (was Re: draft-ie… Brzozowski, John
- Re: "6to4 damages the Internet" (was Re: draft-ie… TJ
- Re: IPv6 traffic distribution james woodyatt
- RE: IPv6 traffic distribution Michel Py
- Re: IPv6 traffic distribution Keith Moore
- Re: "6to4 damages the Internet" (was Re: draft-ie… Masataka Ohta
- Re: "6to4 damages the Internet" (was Re: draft-ie… Keith Moore
- Re: "6to4 damages the Internet" (was Re: draft-ie… Philip Homburg
- Re: "6to4 damages the Internet" (was Re: draft-ie… Philip Homburg
- RE: IPv6 traffic distribution Worley, Dale R (Dale)
- Re: [v6ops] 6to4v2 (as in ripv2)? Cameron Byrne
- Re: [v6ops] 6to4v2 (as in ripv2)? Jeroen Massar
- Re: [v6ops] 6to4v2 (as in ripv2)? Jeroen Massar
- Re: [v6ops] 6to4v2 (as in ripv2)? Philip Homburg
- Re: [v6ops] 6to4v2 (as in ripv2)? Jeroen Massar
- Re: IPv6 traffic distribution Lorenzo Colitti
- RE: IPv6 traffic distribution Michel Py
- Re: IPv6 traffic distribution Lorenzo Colitti
- Re: IPv6 traffic distribution Tim Chown
- RE: IPv6 traffic distribution Michel Py
- Re: IPv6 traffic distribution Thierry Ernst
- Re: "6to4 damages the Internet" (was Re: draft-ie… Masataka Ohta
- Re: IPv6 traffic distribution Brian E Carpenter
- Re: "6to4 damages the Internet" (was Re: Martin Rex
- Re: "6to4 damages the Internet" (was Re: Philip Homburg
- Re: IPv6 traffic distribution George Michaelson
- Re: "6to4 damages the Internet" (was Re: Cameron Byrne
- Re: IPv6 traffic distribution Keith Moore
- Re: "6to4 damages the Internet" (was Re: Masataka Ohta
- RE: IPv6 traffic distribution Michel Py
- Re: IPv6 traffic distribution Joel Jaeggli
- RE: IPv6 traffic distribution Michel Py
- Re: IPv6 traffic distribution Keith Moore
- Re: IPv6 traffic distribution Keith Moore
- Re: IPv6 traffic distribution Ole Troan
- Re: IPv6 traffic distribution Joel Jaeggli
- Re: IPv6 traffic distribution George Michaelson
- Re: "6to4 damages the Internet" (was Re: Masataka Ohta
- Re: 6to4v2 (as in ripv2)? Rémi Després
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Rémi Després
- Re: IPv6 traffic distribution Rémi Després
- Re: IPv6 traffic distribution Joel Jaeggli
- Re: IPv6 traffic distribution Rémi Després
- Re: 6to4v2 (as in ripv2)? Keith Moore
- Re: IPv6 traffic distribution Rémi Després
- RE: 6to4v2 (as in ripv2)? Michel Py
- Re: IPv6 traffic distribution George Michaelson
- Re: 6to4v2 (as in ripv2)? Rémi Després
- RE: 6to4v2 (as in ripv2)? Michel Py
- RE: 6to4v2 (as in ripv2)? Christian Huitema
- Re: 6to4v2 (as in ripv2)? Philip Homburg
- RE: 6to4v2 (as in ripv2)? Templin, Fred L
- Re: [v6ops] 6to4v2 (as in ripv2)? Mark Andrews
- What is Native IPv6 Michel Py
- Re: IPv6 traffic distribution Brzozowski, John
- Re: What is Native IPv6 JORDI PALET MARTINEZ
- Re: What is Native IPv6 Roger Jørgensen
- Re: What is Native IPv6 Keith Moore
- Re: What is Native IPv6 Philip Homburg
- RE: What is Native IPv6 Michel Py
- Re: What is Native IPv6 Philip Homburg
- Re: "6to4 damages the Internet" (was Re: Mark Atwood
- Re: "6to4 damages the Internet" (was Re: Masataka Ohta
- Re: [v6ops] 6to4v2 (as in ripv2)? Jeroen Massar
- RE: [v6ops] 6to4v2 (as in ripv2)? Frank Bulk
- Re: [v6ops] 6to4v2 (as in ripv2)? Keith Moore
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Ronald Bonica