[OSPF] OSPF over IPv4: use case example
RJ Atkinson <rja.lists@gmail.com> Mon, 03 March 2014 10:41 UTC
Return-Path: <rja.lists@gmail.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D267F1A0E1F for <ospf@ietfa.amsl.com>; Mon, 3 Mar 2014 02:41:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 8sx-2udDsQ0Y for <ospf@ietfa.amsl.com>; Mon, 3 Mar 2014 02:41:15 -0800 (PST)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 9A4081A0C0B for <ospf@ietf.org>; Mon, 3 Mar 2014 02:41:12 -0800 (PST)
Received: by mail-wg0-f49.google.com with SMTP id b13so1140267wgh.8 for <ospf@ietf.org>; Mon, 03 Mar 2014 02:41:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version; bh=3mlNzgJbTb80s2Qv49FBG2leVXD9xJoQGTLGhTM6970=; b=gO8Aeg2dcuoIhEa5KqsuqJbgKY0Ncs8hG6jmn8t4W6qtgu4YWKVns/VizXN/U0/QD2 wbMVsu94JZA2hdRFpjJjFDL2WBo7zS8jwf18jStjQBRPUOACqJAVkVrZffOT8aEvZ0fH TNJbCIsXyANdRsiyhsf1BXf2ByPSmggyMRcH5BNQpZH3Fsi4YsRwnr/HKnVdioAJqqfN rsq0HLONb2u1Yw9Zrs46XTYnx7GTMVLrl2JmqMEj1bK2FubzcE/rGUJbED5lyLLh/2sC puP0qF6BPmd0o+fkqAdmm9ZXp0dTKV/mLgi++XKc2zX51iDLwG1VmCj9/If+Mccufkm+ FoPw==
X-Received: by 10.194.190.10 with SMTP id gm10mr6012413wjc.55.1393843269241; Mon, 03 Mar 2014 02:41:09 -0800 (PST)
Received: from dhcp-b378.meeting.ietf.org (dhcp-b378.meeting.ietf.org. [31.133.179.120]) by mx.google.com with ESMTPSA id t5sm33182426wjw.15.2014.03.03.02.41.08 for <ospf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Mar 2014 02:41:08 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Mon, 03 Mar 2014 05:41:06 -0500
Message-Id: <328D06B6-9CA8-44DB-A3E8-71CDB878C7F8@gmail.com>
To: ospf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/tHSa72BoLeS5LfoFlhS8p1Y5vUs
Subject: [OSPF] OSPF over IPv4: use case example
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Mar 2014 10:41:19 -0000
Hi, During the OSPF meeting (taking place now), Abhay recently asked why IPv6 link-local addressing is not a sufficient solution for OSPFv3 deployments (with AF extension) in IPv4-only networks. As we discussed during the meeting, there are some deployed link types that do not yet support IPv6 packets *at all*. However, one imagines that over time, such links will have equipment upgrades to have full dual-stack (IPv4 + IPv6) support. Using OSPFv3/IPv4 now with the AF extension -- and later migrating to OSPFv3 -- can reduce operations costs significantly in at least some deployments that I'm familiar with. For example, some deployed IP/VSAT terminals either (A) have Ethernet interfaces that only support ARP and IPv4 [e.g., using EtherType to filter in hardware] OR (B) have serial interfaces that again only support IPv4/PPP packets. ASIDE with more context: For those who don't use SATCOM much, The term VSAT is precisely defined as "Very Small Aperture Terminal". "Very Small Aperture" typically means that the SATCOM dish on the ground is roughly 1m in diameter, rather than the rather larger SATCOM dishes used in some other deployments. VSATs are quite commonly used around the whole globe, in both developed and less developed regions. Within North America they commonly are used to connect retail sites (e.g. banks, petrol stations, consumer electronics stores) back to the central site for that business. Separately, it would not be odd for a VSAT deployment to have an uplink speed that is ~10% of the downlink speed. Yours, Ran Atkinson
- [OSPF] OSPF over IPv4: use case example RJ Atkinson
- Re: [OSPF] OSPF over IPv4: use case example Acee Lindem