Re: [Idr] Issue 2: Auto-configuration Requirements - LSVR layer 3 discovery and liveness requirements

"Susan Hares" <shares@ndzh.com> Mon, 10 June 2019 19:29 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD9861201E5; Mon, 10 Jun 2019 12:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.948
X-Spam-Level:
X-Spam-Status: No, score=0.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 snjrTuBGpGb5; Mon, 10 Jun 2019 12:29:20 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0835C12015E; Mon, 10 Jun 2019 12:29:19 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=174.25.175.69;
From: "Susan Hares" <shares@ndzh.com>
To: <idr@ietf.org>
Cc: <lsvr@ietf.org>
Date: Mon, 10 Jun 2019 15:29:15 -0400
Message-ID: <01e901d51fc2$cad8a5d0$6089f170$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01EA_01D51FA1.43C94FC0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdUfwspQ4Ro1opOBT+K1Xn6u2xHiYg==
Content-Language: en-us
X-Antivirus: AVG (VPS 190610-6, 06/10/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/YcISb52A2Ucd_fiUkevNZ3O3ObQ>
Subject: Re: [Idr] Issue 2: Auto-configuration Requirements - LSVR layer 3 discovery and liveness requirements
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2019 19:29:25 -0000

 

Requirements list from draft-ietf-lsvr-l3dl-00

Layer 3 Discovery and Liveness (L3DL) provides brutally simple
   mechanisms for devices to
 
   o  Discover unique identities of devices/ports/... on a logical link,
 
   o  Run Layer 2 keep-alive messages for session continuity,
 
   o  Discover each other's unique endpoint identification,
 
   o  Discover mutually supported encapsulations, e.g.  IP/MPLS,
 
   o  Discover Layer 3 IP and/or MPLS addressing of interfaces of the
      encapsulations,
 
   o  Enable layer 3 link liveness such as BFD, and finally
 
   o  Present these data, using a very restricted profile of a BGP-LS
      [RFC7752 <https://tools.ietf.org/html/rfc7752> ] API, to BGP-SPF which
computes the topology and builds
      routing and forwarding tables.

 

If the a authors of this draft would suggest a different list of
requirements, 

please just respond to this email. 

 

Cheerily, Sue Hares 

 

 

 

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Monday, June 10, 2019 3:26 PM
To: idr@ietf.org
Cc: lsvr@ietf.org
Subject: [Idr] Issue 2: Auto-configuration Requirements

 

IDR WG: 

 

Does IDR think that we should include a generalized auto-discovery protocol
in the IDR WG charter? 

If so, should it be for WAN or Data Center or IPRAN topologies (grid/ring)? 

 

LSVR is progressing with Layer 3 liveness in  draft-ietf-lsvr-l3dl-00

https://datatracker.ietf.org/doc/draft-ietf-lsvr-l3dl/

 

LSVR is progressing because IDR did not have a consensus on requirements for
a general Layer 3 liveness protocol in 2018. 

 

This thread is to discuss the requirements for a generalized or 

a specific auto-discovery protocol associated with BGP. 

 

My next posts will contain the requirements for LSVR Layer 3 liveness and 

draft-xu-idr-neighbor-autodiscovery requirements 

 

https://datatracker.ietf.org/doc/draft-xu-idr-neighbor-autodiscovery/

 

Sue Hares