IETF Logo Mail Archive

Re: [Lsvr] [Idr] Issue 2: Auto-configuration Requirements - draft-xu-idr-neighbor-autodiscovery-requirements

Robert Raszuk <rraszuk@gmail.com> Mon, 10 June 2019 19:44 UTC

Return-Path: <rraszuk@gmail.com>
X-Original-To: lsvr@ietfa.amsl.com
Delivered-To: lsvr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD6AC12006B; Mon, 10 Jun 2019 12:44:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 GUXfJlOgBLiY; Mon, 10 Jun 2019 12:44:52 -0700 (PDT)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (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 AAC8F1200CD; Mon, 10 Jun 2019 12:44:52 -0700 (PDT)
Received: by mail-pg1-x531.google.com with SMTP id v9so3857216pgr.13; Mon, 10 Jun 2019 12:44:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2nRYsX5U1GYW56gkmdjGaYcwthf90egSrxX0dq4gQsg=; b=ESrqyzuxTIkwBXn0aadRImEQQCja84lXUX0YVKWQg2By6ab8weNwhp/51BZxMTdk7Q ntrZcmTkH24VMqLOJt9+gQLjcWaUTZiL5BsZ6r8swkvJQc9hY7fRyy92e5DkoqX2+jwC ygFgHjo+5ySXTrsDvdPcIq4BH0Mqu25DP3dnHukAf/b7I4TRwpBY/6BhPrJDmQ3L7ZWF ZW17d6dgTo+wRKjvtVj4X9PkgzyGUTxCXMgKM2AYkDuuBpoYe3Fulm8zDKosu2GLB1MP yeWL3LHuy/pqd9FVZjRyBGV2lB1Bt7P+hji1cnBevPqvp525oVXP6Gi+SlP+vq2Jrovm 0R8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2nRYsX5U1GYW56gkmdjGaYcwthf90egSrxX0dq4gQsg=; b=NB8iz+EajDop5TB+4yehLEsYAXr22xBnqASdUdc1s2aHl8lgORX6hec9dQfzZ+s107 81oL7TAwQuFM+RTI1wvmeH/D7JaqXu6XlJ7aIwazdshA6c4qpY+AiBmoIEg7e5Mem+hO R5o/91J2uywoGEo6caAqXV795VhXOjoUooM74LEUnzdbRrCs7Wbe/2tc0G7Opy5ZK2Iu KwC9Mn0WsR9I6SHfyMvh7utpmcQn5Z+hT0M8BGL0lQJo1IPZ1TqUgZmY7RSMmkA2/r6p 5nEvWJoWiE88KXMKQ6FCdZfHKfUup/t4NYN0GO6GEL0UbyjIKV9wzZM3R2HKhzXq+zkb BCfA==
X-Gm-Message-State: APjAAAXGCr0Cy9j8ORZ1HmI5y67oEwOVdrTx9qMrPwwUPhF4IO+chbCW J6Tcvq0RS55xwDNSE8FhnNP+yV4UzPYpypkjGRx/CoqxnLisKQ==
X-Google-Smtp-Source: APXvYqxJ7gkIfV+NK0PVype9zYCFFjinObK8KBE36MzsOSOmhBwoicu6TynICO1mCgZRQ6fkYWwp4gF2pNQR47IlXno=
X-Received: by 2002:a63:5009:: with SMTP id e9mr16739099pgb.396.1560195891478; Mon, 10 Jun 2019 12:44:51 -0700 (PDT)
MIME-Version: 1.0
References: <020201d51fc2$e8b748e0$ba25daa0$@ndzh.com>
In-Reply-To: <020201d51fc2$e8b748e0$ba25daa0$@ndzh.com>
From: Robert Raszuk <rraszuk@gmail.com>
Date: Mon, 10 Jun 2019 21:44:41 +0200
Message-ID: <CA+b+ERm5CHmCiDF8MfoaSAOvse+Yk6aug3bUrS1Vveku1G5wQA@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: idr wg <idr@ietf.org>, lsvr@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e4476b058afd696b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/rveSvBDFasJKyjQgDWo1-K0bp-Y>
Subject: Re: [Lsvr] [Idr] Issue 2: Auto-configuration Requirements - draft-xu-idr-neighbor-autodiscovery-requirements
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Vector Routing <lsvr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsvr>, <mailto:lsvr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr/>
List-Post: <mailto:lsvr@ietf.org>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsvr>, <mailto:lsvr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2019 19:44:55 -0000

Hi Sue,

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


Yes. At least for WAN.


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

There has been quite a bit of work history on WAN auto discovery for BGP
(started with IBGP then extended also to EBGP).

https://tools.ietf.org/html/draft-raszuk-idr-bgp-auto-discovery-05

If LSVR likes to address directly connected peer discovery that to me is
quite separate problem space and they are welcome to proceed.

It would be best if different name is chosen to avoid confusion and that
such peer discovery is not just made exclusive for BGP. BGP while some do
configure it in DC or IP RAN networks tomorrow could be replaced by
different protocol yet peer discovery requirement could stay the same.

Thx,
R.


*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
>
>
> _______________________________________________
> Lsvr mailing list
> Lsvr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsvr
>

v2.23.0 | Report a Bug | By Email