[BEHAVE] IPv4 address literals on websites
"Dan Wing" <dwing@cisco.com> Mon, 18 October 2010 18:00 UTC
Return-Path: <dwing@cisco.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF8303A6E3B for <behave@core3.amsl.com>; Mon, 18 Oct 2010 11:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.411
X-Spam-Level:
X-Spam-Status: No, score=-110.411 tagged_above=-999 required=5 tests=[AWL=0.188, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hi7a+dGn3dis for <behave@core3.amsl.com>; Mon, 18 Oct 2010 11:00:56 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 553173A6E41 for <behave@ietf.org>; Mon, 18 Oct 2010 11:00:54 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFALMovEyrR7H+/2dsb2JhbACTMIEjjFpxo1CcQ4IXeAGCOQSEVA
X-IronPort-AV: E=Sophos;i="4.57,345,1283731200"; d="scan'208";a="271297528"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-5.cisco.com with ESMTP; 18 Oct 2010 18:02:11 +0000
Received: from dwingWS ([10.32.240.194]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o9II2B3S014125 for <behave@ietf.org>; Mon, 18 Oct 2010 18:02:11 GMT
From: Dan Wing <dwing@cisco.com>
To: behave@ietf.org
Date: Mon, 18 Oct 2010 11:02:11 -0700
Message-ID: <2e0301cb6eee$968dd360$c3a97a20$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Actu7pZUqPLDuXphTfy73oWgHU2BKg==
Content-Language: en-us
Subject: [BEHAVE] IPv4 address literals on websites
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 18:00:56 -0000
I have been receiving comments about IPv4 address literals being found on IPv4 websites, but without specifics of the URLs containing such IPv4 address literals. As we know, such content is inaccessible by IPv6-only clients going through a NAT64/DNS64 unless special steps are taken. It would be beneficial to the community to have a sense of how often and where IPv4 address literals occur on the Internet and impact users visiting a website. To that end, several months ago Cameron Byrne created http://groups.google.com/group/ipv4literals. If you have encountered an IPv4 address literal, it would be useful to add it to that web page. (The page requires a Google login; those logins are free). Currently, only 3 websites are listed there -- Formula1 video streaming, mobile.nytimes.com, and Amazon video streaming. -d