Re: [v6ops] v6ops Digest, Vol 52, Issue 41

Mark Andrews <marka@isc.org> Sat, 13 December 2014 22:15 UTC

Return-Path: <marka@isc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBC331A03A7 for <v6ops@ietfa.amsl.com>; Sat, 13 Dec 2014 14:15:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.89
X-Spam-Level:
X-Spam-Status: No, score=-0.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RC7nCgGiQq45 for <v6ops@ietfa.amsl.com>; Sat, 13 Dec 2014 14:15:07 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D10C51A1A58 for <v6ops@ietf.org>; Sat, 13 Dec 2014 14:15:06 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP id B67AF349633; Sat, 13 Dec 2014 22:15:04 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 59585160067; Sat, 13 Dec 2014 22:19:46 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 22CEB160066; Sat, 13 Dec 2014 22:19:46 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id CDB2E2560155; Sun, 14 Dec 2014 09:15:01 +1100 (EST)
From: Mark Andrews <marka@isc.org>
In-reply-to: Your message of "Sun, 14 Dec 2014 09:04:05 +1100."
Date: Sun, 14 Dec 2014 09:15:01 +1100
Message-Id: <20141213221501.CDB2E2560155@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/y8jkw9qGaJLpB0nDkwJgb8UxF3Y
Cc: Tariq Saraj <tariqsaraj@gmail.com>, v6ops@ietf.org
Subject: Re: [v6ops] v6ops Digest, Vol 52, Issue 41
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Dec 2014 22:15:09 -0000

Mark Andrews writes:
> 
> In message <CAAdbxrpgsdJJ0exP435JSB=m7RV=yEYw8-cOx9xfcAzipkoy0g@mail.gmail.co
> m>
> , Tariq Saraj writes:
> > 
> > There are some issues with 6rd as well, IPv6 with all its powerful features
> > is still under critical objections in academia just because of the urgency
> > shown by IETF in standardizing protocols like 6to4 and 6rd. 6to4 clearly
> > mentioned that it cannot support multicast at layer-3, on the other end 6rd
> > claimed that multicast can be provided, my question is that while
> > standardizing 6rd which at that time was just supporting unicast traffic
> > traversing across IPv4 network and its still not matured enough to provide
> > multicast support yet in its functionality other than using some proxy
> > support for multicast traffic. why It was standardized ?
> 
> 6to4 and 6rd are interim solutions for delivering IPv6 over IPv4.
> They were standardized so that manufactures could ship products
> that interoperate.
> 
> Engineering is all about trade offs.  With 6to4 and 6rd it is about
> delivering IPv6 unicast in a timely manner while waiting for the
> intermediate network components to be upgraded to support IPv6.
> 
> If you need IPv6 multicast then you need to arrange for it to be
> delivered.  You can still run multicast tunnels over 6to4 and 6rd
> if you need to.  They just don't supply multicast natively.
> 
> I suspect you will find you will need to do this even with native
> IPv6 as many ISP's are in the business of delivering global multicast

Missed the key word "not"

	are *not* in the business of delivering global multicast

> traffic.
> 
> > a common
> > university level student is considering IPv6 nothing more than just a large
> > address space. The support for multicast traffic is increasing every day at
> > application level. My request at this forum is to consider 6rd along with
> > the 6to4 so that in future both of these protocols not to become a part of
> > any network device. I personally feels that instead of supporting to
> > promote the IPv6 both of these protocols are becoming obstacles in this
> > regards. I prefer using GRE over these automatic tunneling mechanisms at
> > least GRE supports multicast on network layer and let the application
> > program to design his/her application in more different ways.
> 
> Mark
> -- 
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org