Passive Interface Attribute
draft-wang-lsr-passive-interface-attribute-00

Document Type Active Internet-Draft (individual)
Last updated 2020-01-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
LSR Working Group                                                A. Wang
Internet-Draft                                             China Telecom
Intended status: Standards Track                                   Z. Hu
Expires: July 13, 2020                               Huawei Technologies
                                                        January 10, 2020

                      Passive Interface Attribute
             draft-wang-lsr-passive-interface-attribute-00

Abstract

   This document describes the mechanism that can be used to
   differentiate the passive interfaces from the normal interfaces
   within ISIS domain.

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 https://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 July 13, 2020.

Copyright Notice

   Copyright (c) 2020 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
   (https://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.

Wang & Hu                 Expires July 13, 2020                 [Page 1]
Internet-Draft                     PIA                      January 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   2
   3.  Scenario Description  . . . . . . . . . . . . . . . . . . . .   3
   4.  Passive Interface Attribute . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   Passive interfaces are used commonly within operator or enterprise
   networks, especially at the boundary of different IGP domains.  Using
   passive interface can keep the address that associated with it is
   reachable within the domain it belongs to but no other link
   information is leaked to the other side in another domain.

   For operator which runs different IGP domains that interconnect with
   each other, there is desire that to get the inter-as topology
   information as that described in
   [I-D.ietf-idr-bgpls-inter-as-topology-ext].  If the router that run
   BGP-LS within one IGP domain can distinguish the passive
   interfaces(also the links between two boundary) from the other normal
   interfaces, then it is easy for them to report these link in the
   "Stub Link NLRI" via the BGP-LS.

   OSPF has the mechanism as described in [RFC2328] to label the passive
   interface, but ISIS protocol has no such attribute to label the
   passive interface.

   This document introduces the mechanism that can be used in such
   situation, to label the passive interface via the newly defined
   passive interface attribute.

2.  Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119] .

Wang & Hu                 Expires July 13, 2020                 [Page 2]
Internet-Draft                     PIA                      January 2020

3.  Scenario Description

   Figure1 illustrates the topology scenario when ISIS/OSPF is running
   in different domain.  B1, B3 are border routers within IGP domain A,
   B2, B4 are border routers within domain B.  S1-S4 are the internal
   routers within domain A, T1-T4 are the internal routers within domain
   B.  The two domain are interconnected via the links between B1/B2 and
   B3/B4.

   Passive interfaces are enabled in the links between B1/B2 and B3/B4
Show full document text