[OSPF] OSPFv2 operation on broadcast media with "slacked"/"discontinuous" IP addressing

David Lamparter <equinox@opensourcerouting.org> Sat, 23 June 2012 13:57 UTC

Return-Path: <equinox@diac24.net>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73FB021F844F for <ospf@ietfa.amsl.com>; Sat, 23 Jun 2012 06:57:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dZieF+Mm0DMw for <ospf@ietfa.amsl.com>; Sat, 23 Jun 2012 06:57:48 -0700 (PDT)
Received: from spaceboyz.net (spaceboyz.net [IPv6:2001:8d8:81:5c0::1]) by ietfa.amsl.com (Postfix) with ESMTP id CFC3221F844D for <ospf@ietf.org>; Sat, 23 Jun 2012 06:57:46 -0700 (PDT)
Received: from jupiter.n2.diac24.net ([2001:8d8:81:5c2:21b:fcff:fe4c:9e6f]) by spaceboyz.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from <equinox@diac24.net>) id 1SiQqL-0001Xc-LG for ospf@ietf.org; Sat, 23 Jun 2012 15:57:41 +0200
Received: from equinox by jupiter.n2.diac24.net with local (Exim 4.77) (envelope-from <equinox@diac24.net>) id 1SiQQu-00Fm08-Mw for ospf@ietf.org; Sat, 23 Jun 2012 15:31:24 +0200
Date: Sat, 23 Jun 2012 15:31:24 +0200
From: David Lamparter <equinox@opensourcerouting.org>
To: ospf@ietf.org
Message-ID: <20120623133124.GA3653120@jupiter.n2.diac24.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="zYM0uCDKw75PZbzx"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: equinox@diac24.net
Subject: [OSPF] OSPFv2 operation on broadcast media with "slacked"/"discontinuous" IP addressing
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 23 Jun 2012 13:57:48 -0000

Hi,


out of a rather funny misunderstanding of RFC 5309, I've ended up with
half an implementation of OSPF running in ignorance of the IP subnet
mask on a broadcast network.  After cleaning up the misunderstanding and
taking a step back, I found draft-ietf-ospf-hybrid-bcast-and-p2mp, which
I expected to contain a note about this, but no such thing.

The general idea would be to operate a broadcast medium with a /32
subnet mask, possibly unnumbered, and allowing adjacencies with just
about anything that sends a Hello (and passes auth).

The link can operate as regular broadcast, hybrid-bcast-p2mp, or P-t-P
(the last would amount to RFC 5309 with the detail that the peer address
is not known up front.)

(For OSPFv3, this is obviously not interesting since with link-local
addresses, there is no notion of similar same-subnet restrictions.)

I haven't found anything on this - is this mode of operation already
described somewhere?


Cheers,

David