Hiding Transit-only Networks in OSPF
draft-ietf-ospf-prefix-hiding-06

The information below is for an old version of the document
Document Type Active Internet-Draft (ospf WG)
Last updated 2012-12-04
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation::AD Followup
Telechat date
Needs a YES. Needs 6 more YES or NO OBJECTION positions to pass.
Responsible AD Stewart Bryant
IESG note Acee Lindem (acee.lindem@ericsson.com) is the document shepherd.
Send notices to ospf-chairs@tools.ietf.org, draft-ietf-ospf-prefix-hiding@tools.ietf.org
OSPF Working Group                                               Y. Yang
Internet-Draft                                                 A. Retana
Updates: 2328, 5340 (if approved)                                 A. Roy
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: June 7, 2013                                   December 4, 2012

                  Hiding Transit-only Networks in OSPF
                 <draft-ietf-ospf-prefix-hiding-06.txt>

Abstract

   A transit-only network is defined as a network connecting routers
   only.  In OSPF, transit-only networks are usually configured with
   routable IP addresses, which are advertised in Link State
   Advertisements (LSAs) but not needed for data traffic.  In addition,
   remote attacks can be launched against routers by sending packets to
   these transit-only networks.  This document presents a mechanism to
   hide transit-only networks to speed up network convergence and reduce
   remote attack vulnerability.

   In the context of this document, 'hiding' implies that the prefixes
   are not installed in the routing tables on OSPF routers. In some
   cases, IP addresses may still be visible when using OSPFv2.

   This document updates RFC 2328 and RFC 5340.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 17, 2013.

 

Yang, et al.              Expires June 7, 2013                  [Page 1]
Internet-Draft    Hiding Transit-only Networks in OSPF  December 4, 2012

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

 

Yang, et al.              Expires June 7, 2013                  [Page 2]
Internet-Draft    Hiding Transit-only Networks in OSPF  December 4, 2012

Table of Contents

   1. Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1. Requirements notation . . . . . . . . . . . . . . . . . . .  4
   2. Hiding IPv4 Transit-only Networks in OSPFv2 . . . . . . . . . .  4
     2.1. Point-to-Point Networks . . . . . . . . . . . . . . . . . .  4
       2.1.1. Advertising Point-to-Point Networks . . . . . . . . . .  4
       2.1.2. Hiding Point-to-Point Networks  . . . . . . . . . . . .  5
     2.2. Broadcast Networks  . . . . . . . . . . . . . . . . . . . .  5
       2.2.1. Advertising Broadcast Networks  . . . . . . . . . . . .  6
       2.2.2. Hiding Broadcast Networks . . . . . . . . . . . . . . .  6
         2.2.2.1. Sending Network-LSA . . . . . . . . . . . . . . . .  6
         2.2.2.2. Receiving Network-LSA . . . . . . . . . . . . . . .  7
           2.2.2.2.1. Backward Compatibility  . . . . . . . . . . . .  7
     2.3. Non-Broadcast Networks  . . . . . . . . . . . . . . . . . .  7
       2.3.1. NBMA  . . . . . . . . . . . . . . . . . . . . . . . . .  7
       2.3.2. Point-to-MultiPoint . . . . . . . . . . . . . . . . . .  8
         2.3.2.1. Advertising Point-to-MultiPoint Networks  . . . . .  9
         2.3.2.2. Hiding Point-to-MultiPoint Networks . . . . . . . .  9
   3. Hiding IPv6 Transit-only Networks in OSPFv3 . . . . . . . . . . 10
     3.1. Hiding AF Enabled Transit-only Networks in OSPFv3 . . . . . 10
   4. Operational Considerations  . . . . . . . . . . . . . . . . . . 11
     4.1. Forwarding Address  . . . . . . . . . . . . . . . . . . . . 11
     4.2. Virtual Links . . . . . . . . . . . . . . . . . . . . . . . 11
     4.3. Unnumbered Interfaces . . . . . . . . . . . . . . . . . . . 12
   5. Security Considerations . . . . . . . . . . . . . . . . . . . . 12
   6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 13
Show full document text