Re: [OSPF] OSPF NBMA interface type

Acee Lindem <> Fri, 05 July 2013 13:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AAC0521F9943 for <>; Fri, 5 Jul 2013 06:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.446
X-Spam-Status: No, score=-2.446 tagged_above=-999 required=5 tests=[AWL=0.153, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4cm+KB3tUJ7F for <>; Fri, 5 Jul 2013 06:29:27 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 1F0CA21F994C for <>; Fri, 5 Jul 2013 06:29:27 -0700 (PDT)
X-AuditID: c6180641-b7f986d000007a82-fa-51d6ca3590cd
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 49.2D.31362.53AC6D15; Fri, 5 Jul 2013 15:29:26 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.02.0328.009; Fri, 5 Jul 2013 09:29:26 -0400
From: Acee Lindem <>
To: Glen Kent <>
Thread-Topic: OSPF NBMA interface type
Thread-Index: AQHOeUxdlcRaqOWDmkaNGRsvDhSZ2JlWV8qA
Date: Fri, 05 Jul 2013 13:29:25 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrELMWRmVeSWpSXmKPExsUyuXSPn67ZqWuBBvtP8lvsOfGexaLl3j12 ByaPnbPusnssWfKTKYApissmJTUnsyy1SN8ugSvj3LRjjAXHOSpeHnrF1sD4jK2LkYNDQsBE YvFE9y5GTiBTTOLCvfVAYS4OIYGjjBK7Nz1ngnCWMUos/jqPFaSKTUBH4vmjf8wgzSICyhJv bqaAhJmBzMddq9lAbGEBVYkpU9+xg9giAmoSO35fZoEoN5I4tzATJMwioCJxctlTFhCbV8Bb Ys7dVrBzhAQCJK7/dwAJcwoEShx7eYURxGYEOu37qTVMEJvEJW49mc8EcbKAxJI955khbFGJ l4//sULYyhLf5zxigajXkViw+xMbhG0tsezLXUYIW1ti2cLXzBAnCEqcnPmEZQKj+CwkK2Yh aZ+FpH0WkvZZSNoXMLKuYuQoLU4ty003MtzECIynYxJsjjsYF3yyPMQozcGiJM67Qe9MoJBA emJJanZqakFqUXxRaU5q8SFGJg5OqQZGrrNL7Lnj9S+W3rnDzRsTuX7FhhvxucwTP+3IlZ2f 9nXe7DMnDBNfufFv13ivlx4gE/GmuH/Op8ftxx7+NzHtV1oqrq6xquv+r2IpUV6dWbFP1qo6 ciVHinYJfP8RZP+z73uQF/uRWfe7RP7mPz6aO/+P8cEE1fcv3R39L87WTysx6F/H0ZquxFKc kWioxVxUnAgABfEMo3UCAAA=
Cc: "" <>
Subject: Re: [OSPF] OSPF NBMA interface type
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 05 Jul 2013 13:29:33 -0000

Hi Glen,
With the convergence to ethernet everywhere, there is much less of a requirement for other OSPF topologies. However, P2MP is still very relevant in wireless and we now have the hybrid interface (RFC 6845). With Ericsson IPOS, we also use P2MP for subscriber OSPF adjacencies where a single interface can support many subscribers each with some form of explicit or implied encap for demuxing each individual subscriber.

I don't see much requirement for NBMA but I'm sure there are deployments making use of it.  


On Jul 5, 2013, at 2:53 AM, Glen Kent wrote:

> Hi,
> These days people only have OSPF interface type as point-to-point and broadcast. I understand that NBMA was required for technologies that inherently dont support bcast, but where packets need to be sent to multiple nodes (like ATM).
> Given that ATM and Frame Relay networks are mostly out, when would we use an OSPF interface type as NBMA or point-to-multipoint.
> Is it in some wireless domains that we will use this?
> Glen