Re: [OSPF] OSPF over IPv4: use case example

Acee Lindem <acee.lindem@ericsson.com> Sun, 09 March 2014 16:31 UTC

Return-Path: <acee.lindem@ericsson.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 350441A0268 for <ospf@ietfa.amsl.com>; Sun, 9 Mar 2014 09:31:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Level:
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_20=-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 7oPLsrUb6t2o for <ospf@ietfa.amsl.com>; Sun, 9 Mar 2014 09:31:31 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id D4D111A0277 for <ospf@ietf.org>; Sun, 9 Mar 2014 09:31:30 -0700 (PDT)
X-AuditID: c6180641-b7f2f8e000002cdc-27-531c94750ed8
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id C8.13.11484.5749C135; Sun, 9 Mar 2014 17:19:02 +0100 (CET)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.02.0387.000; Sun, 9 Mar 2014 12:31:25 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: RJ Atkinson <rja.lists@gmail.com>, "ospf@ietf.org" <ospf@ietf.org>
Thread-Topic: [OSPF] OSPF over IPv4: use case example
Thread-Index: AQHPO7UD41b2ErhEqEiQ1wH2CEIvBw==
Date: Sun, 09 Mar 2014 16:31:24 +0000
Message-ID: <CF40BB48.29C2B%acee.lindem@ericsson.com>
In-Reply-To: <328D06B6-9CA8-44DB-A3E8-71CDB878C7F8@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.6.130613
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2E200BA8ACC2934286E9921B5B2A8D6A@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrJLMWRmVeSWpSXmKPExsUyuXRPrG7ZFJlgg1t3+C1a7t1jt7i/o4fR gclj56y77B5LlvxkCmCK4rJJSc3JLEst0rdL4MrYtfg0a8E6/or1kx6wNDBu4eli5OSQEDCR aHuzmRHCFpO4cG89WxcjF4eQwBFGiW0n2pghnGWMEvPbzzOBVLEJ6Eg8f/SPGcQWEXCT+HH9 BDuILQw0adqzUywQcVOJaw8a2SFsPYljfz8C1XNwsAioSEx8EQAS5gUquf/oBtgYTgFbiYtr H4GVMwId8f3UGrBVzALiEreezGeCOE5AYsme88wQtqjEy8f/WEFsUaDx3bOWs0LElSTmvL7G DNGrI7Fg9yc2CNta4v/ZlawQtrbEsoWvmSFuEJQ4OfMJywRGsVlI1s1C0j4LSfssJO2zkLQv YGRdxchRWpxalptuZLiJERg9xyTYHHcwLvhkeYhRmoNFSZz3y1vnICGB9MSS1OzU1ILUovii 0pzU4kOMTBycUg2MTta/hK7zmsZ9vXFt5bkfLHfvNTGZLErnSbe97rnZRSJXv1bHzawmNT6Q Kc049/riFR8Wb7t0/dC1q4f3Nii79u+S+p/R2Sub49Khoc97b+ax/x7+T1ccWdi79LjIj/en E8sfnZnK4yAS9VgrhXX6tvNr23wi8zYbnZK99JLhCY+W44l25TfTlFiKMxINtZiLihMB1pQV umwCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/PK9t1c9xtAslyJGsgmE1bUoieFk
Subject: Re: [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: Sun, 09 Mar 2014 16:31:33 -0000

Hi Ran, 
We will add this use case to the draft.
Thanks,
Acee 

On 3/3/14 2:41 AM, "RJ Atkinson" <rja.lists@gmail.com> wrote:

>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 mailing list
>OSPF@ietf.org
>https://www.ietf.org/mailman/listinfo/ospf