Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-historic-07.txt
Lorenzo Colitti <lorenzo@google.com> Tue, 11 November 2014 22:23 UTC
Return-Path: <lorenzo@google.com>
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 804BF1A1C06 for <v6ops@ietfa.amsl.com>; Tue, 11 Nov 2014 14:23:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.972
X-Spam-Level:
X-Spam-Status: No, score=-1.972 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] autolearn=ham
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 h-ls15Os6RDk for <v6ops@ietfa.amsl.com>; Tue, 11 Nov 2014 14:23:01 -0800 (PST)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 398EB1A1AF4 for <v6ops@ietf.org>; Tue, 11 Nov 2014 14:23:01 -0800 (PST)
Received: by mail-ie0-f177.google.com with SMTP id tp5so12364526ieb.36 for <v6ops@ietf.org>; Tue, 11 Nov 2014 14:23:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=VWv5qTSnDQZaZPflb19DMy8ZIZDAq7ypoUYJ83HI8u8=; b=WydcamnWyqBI5DBPfwQikEgLTv6bMr4KS0EAIDy7ijGDX0Osnhr0VxjaTTpSDXEnLb U5uYhUNdYOIhHOvqGMaZjvpn+psJBEAmPT22so2IjzHcNAcXubp/MrBfcIPt4ejL4xJL hXlnBVGlQU5I9AjPxMfyPLP1LNSgSXccJ3Qgp2B06qtiSdcLU+NivTZ7zM+FcEsnyMxG jmoo2ZCRQsR+wDQYXz7W/VOvTl1Tq0dKvEXwqqUBYlC4Jvbb33SiNa0dtN6lUfwyRZ/r xow4DOr79vc39AXPL4QtoG6zFYwfzOd3nUjBE+fIdb+cW7a+R+zw5tZ6jo5JGeB5y8Z4 +HYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=VWv5qTSnDQZaZPflb19DMy8ZIZDAq7ypoUYJ83HI8u8=; b=g9+R2m4lelWynAinboDwn2zF+5KFOqINY4gyVbIyL3mtCVhZjfy4TZ0FHruvFJcTMj WS/ue32ri5OVBU63Gi/i0I610b0G42QgeCOmbKvtuEzvHGjGIhDvJ/UCe122XDSX4AqZ oUyh9URfnJ1KZc4k2oV4lHsvGXwKSdv8hCaXr2DMXFVnDwELQVqU3dMQcLc7g+m7qG6d E0Tj0HLzk+SA9qCE8HHYxysRARVJwowiv8omROuU10cDDU71sRfYJXIH3sOr9mZN7TKz rAqooWnwnN0O7Yki3rBP3kxJS6Y4UYr4VUti9a1fqMKsh9Qdn/QX8okvW8nWpynjle4i hvlQ==
X-Gm-Message-State: ALoCoQmPayEst5lB9j4OcTfxBF1NQPpMRITrSh/GMHxPzFYletGOHY+NyjpEiqEQ+RPe71xxTIBq
X-Received: by 10.50.136.133 with SMTP id qa5mr35998217igb.2.1415744580151; Tue, 11 Nov 2014 14:23:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.126.233 with HTTP; Tue, 11 Nov 2014 14:22:39 -0800 (PST)
In-Reply-To: <CADhXe53Jt5AdnrMvsBqw6o45HdZS=Q0ONOZP4gLcthiLR7jdjA@mail.gmail.com>
References: <20141111054026.11197.49784.idtracker@ietfa.amsl.com> <CADhXe53Jt5AdnrMvsBqw6o45HdZS=Q0ONOZP4gLcthiLR7jdjA@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 11 Nov 2014 12:22:39 -1000
Message-ID: <CAKD1Yr02yRK72DK=Tquw5pd5WRmcqiHDR_kNFADmhc_Tdc3m_w@mail.gmail.com>
To: James Woodyatt <jhw@nestlabs.com>
Content-Type: multipart/alternative; boundary="089e0141a76acb1e3905079cb8e0"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/K1qtZFCG5oIxSw30Y5lX5OfcmlA
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-historic-07.txt
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: Tue, 11 Nov 2014 22:23:05 -0000
But if you're a content provider, your stats would show that 6to4 traffic is ~ 0.01% of total traffic, and therefore, you might well choose not to optimize it (even to the extent of not having your own relays and using third-party relays), as long as it works reasonably well. On Tue, Nov 11, 2014 at 12:14 PM, James Woodyatt <jhw@nestlabs.com> wrote: > My comment is not an objection to this draft. I am generally supportive of > this draft. > > I have only one comment, which I suppose *might* rise to the level of a > "complaint" if it were shared by a significant fraction of other > participants, which is simply this: we are retaining RFC 3056 on the > Standards Track, and we are considering an RFC that advises content > providers that supporting 6to4 users with return relays to 2002::/16, maybe > even new ones that aren't currently there, is consistent with Best Current > Practice, but we are not advising anyone else that maybe new deployment of > return relays to 2002::/16 is an idea worth reviewing. Why not? > > Some obvious places to locate a 6to4 return relay spring immediately to > mind, e.g. wherever there is a NAT64 gateway, e.g. in dual-stack customer > edge routers with interfaces numbered with public IPv4 addresses. Anyplace > where an IPv6-only host might be reachable from a host using RFC 3056 (and > not RFC 3068) to get IPv6 packets into the IPv6-only world from some > benighted place where it's the 21st century and still IPv4 is the only > service available to them. > > If I were a content provider (oh wait! I work for one now!), then I might > notice the fact this document singles me out for special attention and > leaves unmolested all the other places where broken 6to4 return relay > service might be just as noticeable to legitimate users of RFC 3056 who are > using manually configured forward relay services. I might think to myself: > hey, why do I need a 6to4 return relay in my network when nobody else has > one, and IETF can't even be bothered to advise them that it's even worth > thinking about? > > As I said above, this is not actually a complaint. It's just a comment, > and if nobody pipes up with a "me too" observation, then that's fine. I > don't have any significant objection to publishing this revision of the > draft now. > > > On Mon, Nov 10, 2014 at 7:40 PM, <internet-drafts@ietf.org> wrote: > >> >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> This draft is a work item of the IPv6 Operations Working Group of the >> IETF. >> >> Title : Deprecating Connection of IPv6 Domains via IPv4 >> Clouds (6to4) >> Authors : Ole Troan >> Brian Carpenter >> Filename : draft-ietf-v6ops-6to4-to-historic-07.txt >> Pages : 7 >> Date : 2014-11-10 >> >> Abstract: >> Experience with the "Connection of IPv6 Domains via IPv4 Clouds >> (6to4)" IPv6 transition mechanism has shown that the mechanism is >> unsuitable for widespread deployment and use in the Internet, >> especially in its anycast mode. This document requests that RFC >> 3068, "An Anycast Prefix for 6to4 Relay Routers", be made obsolete >> and moved to historic status. It also recommends that future >> products should not support 6to4 anycast and that existing >> deployments should be reviewed. >> >> >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/ >> >> There's also a htmlized version available at: >> http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-07 >> >> A diff from the previous version is available at: >> http://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-6to4-to-historic-07 >> >> >> Please note that it may take a couple of minutes from the time of >> submission >> until the htmlized version and diff are available at tools.ietf.org. >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> _______________________________________________ >> v6ops mailing list >> v6ops@ietf.org >> https://www.ietf.org/mailman/listinfo/v6ops >> > > > > -- > james woodyatt <jhw@nestlabs.com> > Nest Labs, Communications Engineering > > _______________________________________________ > v6ops mailing list > v6ops@ietf.org > https://www.ietf.org/mailman/listinfo/v6ops > >
- [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-hist… internet-drafts
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… David Farmer
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Templin, Fred L
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Templin, Fred L
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… James Woodyatt
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Lorenzo Colitti
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Gert Doering
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… David Farmer
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Doug Barton
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Gert Doering
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Doug Barton
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Jeroen Massar
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Ole Troan
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Gert Doering
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Doug Barton
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Gert Doering
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Doug Barton
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Jeroen Massar
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Doug Barton
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Doug Barton
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Jeroen Massar
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Doug Barton
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Jeroen Massar
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-hist… Victor Kuarsingh
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- [v6ops] Missing features of Tunnel Brokers (Was: … Jeroen Massar
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… James Woodyatt
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Alexandru Petrescu