Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BGP Auto Session Setup

"Acee Lindem (acee)" <acee@cisco.com> Sat, 01 February 2020 19:15 UTC

Return-Path: <acee@cisco.com>
X-Original-To: bgp-autoconf@ietfa.amsl.com
Delivered-To: bgp-autoconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C109A120118 for <bgp-autoconf@ietfa.amsl.com>; Sat, 1 Feb 2020 11:15:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.498
X-Spam-Level:
X-Spam-Status: No, score=-14.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=SeZRv2LA; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=e0aUnP9L
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 EjrREmb9gdCi for <bgp-autoconf@ietfa.amsl.com>; Sat, 1 Feb 2020 11:15:39 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BBFC12007C for <bgp-autoconf@ietf.org>; Sat, 1 Feb 2020 11:15:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12525; q=dns/txt; s=iport; t=1580584539; x=1581794139; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=HNEcr7syTh8gDR/nHoFQqJwCt2r2PtjiIqAt9mMxOnI=; b=SeZRv2LAWVXRyxXsco5r1Z44PD8i+ocTACb0wAFC4AyRFrArlCc8+iTr jjbj13/mXQYVZ1QJfHJAhLSog/cDGSfQmxmARZzaIFbK10g+omzBHMz/e cxgxCzbbqowBP0K8sKcI8LIh30FA++kGWPkjruoAPqxS3Ery9qPKjlT8T 0=;
IronPort-PHdr: 9a23:/TnBfRzCyd7nwuHXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YRGN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A+GsHbIQKUhYEjcsMmAl1CcWIBGXwLeXhaGoxG8ERHFI=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AlAADVzTVe/51dJa1lGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYFpAwEBAQELAYEkL1AFbFggBAsqhBSDRgOKd4JfiWGJTIRigS6BJANUCQEBAQwBAS0CAQGEQAIXghokNgcOAgMNAQEEAQEBAgEFBG2FNwyFZgEBAQECARIRHQEBNwEECwIBCBEDAQEBAScDAgICHxEUCQgCBAENBRsHgwQBgX1NAw4gAaE6AoE5iGJ1gTKCfwEBBYJEgl8NC4IMCYE4AYwfGoIAgTgggU5JBy4+ghuCUBaCWjKCLI4PgkiFYJhrRAqCO5IWhCobmwiOYYsPkAsCBAIEBQIOAQEFgVkHK4FYcBVlAYJBUBgNjh2Dc4pTdIEpjXcBAQ
X-IronPort-AV: E=Sophos;i="5.70,391,1574121600"; d="scan'208,217";a="715328352"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 01 Feb 2020 19:15:38 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 011JFcpU011227 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 1 Feb 2020 19:15:38 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 1 Feb 2020 13:15:37 -0600
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 1 Feb 2020 14:15:36 -0500
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Sat, 1 Feb 2020 13:15:35 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jl/6aoAgNxzrbNUjqPp5aPnV3ur+lnmeixA18f9KhMAguOR9JoBWYUoKQmFMW34+aMmLIV8mty90Betqoqq4p/U5FOixuaRoywnAY4xnJ3AdCSCQvuejh5+Ghl5AzHL3asblpoUoLcbfpF3+pmXe/FdZpyKnkH31qYcPnr6oLUwz+0HAcBXw3R4K9KzO/gZ575bjg9ZEzVH0YHH8jWht3gFYNHWKZf8GgU6X6F1HlP1r9ydtOwwp9TLIopiKQnNfNzAJWJL9W9HmDphhk8c7q+J2ncyyXkbm9hQlqKhIYu3b6Gd13cXeglqd9mxpb3hh1bALmw5+1WxmfhrUS+IvtQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HNEcr7syTh8gDR/nHoFQqJwCt2r2PtjiIqAt9mMxOnI=; b=EH8kBUADwh02iIP+6Bx96jvi/12q5GoRpimV44YPY7+vcynJwWa26JiYFYjeytXpyCJ+SIq/jiRHXNMFvztatLVFx+9fvJMfazJ++Gpp0EBWrxBWDo/Il2SHjNcTIucdxEApR8lU2Vmad0JdrlvB5KEnl/lbKQ0rJwrKQEpnwMcr4dfvGlTY5WzIvzlxSlQpENRqjWcthv9lV0jvEVfChi/GUABx6mm4PWu+5TznR3WDCx6WUYlkwwC+aCL08NIPSrumw7LX1Inkml93bP7ZzSsk9QuAB7ka4U2nnhi7jhMjwA2shKCtrqkb8UvuTHZF8wjOr5PD4HaobS8Uaz8QXQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HNEcr7syTh8gDR/nHoFQqJwCt2r2PtjiIqAt9mMxOnI=; b=e0aUnP9LzSAsjb8FJE8ErL8dJiXUPdhFXhFfjCC1GYvOwLHDsE6E6B+d1BvT247FYPhZXJxplYXvEFzWPBX6+qLszJBIlzvKXNzz+5Ju+NUu9noh7KxB5bDVcI7/udeoQ9k4Wd4TUmtEHo9C886Khcfcm8UdZNzwMbFenFkHoDg=
Received: from MWHPR11MB1245.namprd11.prod.outlook.com (10.169.236.11) by MWHPR11MB1742.namprd11.prod.outlook.com (10.175.55.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.27; Sat, 1 Feb 2020 19:15:34 +0000
Received: from MWHPR11MB1245.namprd11.prod.outlook.com ([fe80::1d85:409f:48ef:2d78]) by MWHPR11MB1245.namprd11.prod.outlook.com ([fe80::1d85:409f:48ef:2d78%9]) with mapi id 15.20.2686.031; Sat, 1 Feb 2020 19:15:34 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Jeff Tantsura <jefftant.ietf@gmail.com>, "Dongjie (Jimmy)" <jie.dong@huawei.com>
CC: "bgp-autoconf@ietf.org" <bgp-autoconf@ietf.org>, Robert Raszuk <robert@raszuk.net>
Thread-Topic: [Bgp-autoconf] Fwd: BGP Auto Discovery and BGP Auto Session Setup
Thread-Index: AQHV1tjwAaTQblfyb0qXcv9YDToeZagDDa0AgAAQZwCAAAFKgIAAAFoAgALBJYCAAK9XgP//1juA
Date: Sat, 01 Feb 2020 19:15:34 +0000
Message-ID: <121F6959-842D-43A8-AF01-33D84A2FC8CE@cisco.com>
References: <3c9dde3ee70848369ddfda10cb7e2545@huawei.com> <BDD2024B-7FE1-47BF-8373-E4AF86CA303D@gmail.com>
In-Reply-To: <BDD2024B-7FE1-47BF-8373-E4AF86CA303D@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [2001:420:c0c4:1004::30]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 618eada1-cf71-4205-769d-08d7a74b1d07
x-ms-traffictypediagnostic: MWHPR11MB1742:
x-microsoft-antispam-prvs: <MWHPR11MB17429DCCAAEEA9BCE6931154C2060@MWHPR11MB1742.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 03008837BD
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(376002)(396003)(39860400002)(136003)(346002)(199004)(189003)(53546011)(6506007)(8676002)(81156014)(5660300002)(81166006)(316002)(110136005)(186003)(33656002)(36756003)(71200400001)(478600001)(4326008)(91956017)(6486002)(6512007)(54906003)(2906002)(66446008)(76116006)(86362001)(64756008)(8936002)(2616005)(66556008)(66476007)(66946007); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR11MB1742; H:MWHPR11MB1245.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: pyT/jivnH5F/CvmseFiTtWNy37VCTSaZB+hy8i/YR+LtiNak0SdfQg+g6sx3ep6l7nNMbJ7o4QhXWaEqlPsYxCpJ/Fshzjh4KAm4kRxaIbq3odBnja/pgTLtSvLx5ooz9bqYHGZvK4G624lR+8TznmH/0kFBHQrAQ55l0s6+6I2pw6Ln1dhkt47vSqI6W3SF+unfxBev+Yl2mEgVghwNrx37B85zF4OV/+/wIFE2juXakniBpj8NZxYr7ctVuij2rb18a3GEgVwLDucq8dQJdVNJyACnXY96USO5R/vCw+6vNAomko9dAhtaCYnklAavu21f2PBcHDXAd4jQjeslYaqSjTrh+no932zyZUx/6GSj7ZaJHWit1y2U3YjN5TEKcB5wYqZoJ7qh12KMCiCikvdbX8xA9qLbLdFqQrXph5zidNIeugPqDWHnCE5WvJqd
x-ms-exchange-antispam-messagedata: BPKJ9pYDCAMHjvozNTegn4UJk8dsFNTtxNkBqTZogRkq2EuN3QLJCgDH5R0jZXROQX9zqPoXMXwCLshCHRBoKgm9OISTVQcs4HIcPp9h2aEdZHoyBWOnX9lR8K92J+v1ysuDf+/9Bk3VpYVfWTGksF3Ycgy9yQgrko1/RWrrKc0=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_121F6959842D43A8AF0133D84A2FC8CEciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 618eada1-cf71-4205-769d-08d7a74b1d07
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2020 19:15:34.6559 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: y58uCl+fXtnHr5kWqwb5FELk2EixLZxyqYESKwUtzU996sQwdk9LJ9ikJcF4efYv
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1742
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/GMIY9pT3m95XBpGmoRk3AkKe8J4>
Subject: Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BGP Auto Session Setup
X-BeenThere: bgp-autoconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP autoconfiguration design team discussion list <bgp-autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bgp-autoconf>, <mailto:bgp-autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bgp-autoconf/>
List-Post: <mailto:bgp-autoconf@ietf.org>
List-Help: <mailto:bgp-autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bgp-autoconf>, <mailto:bgp-autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Feb 2020 19:15:42 -0000

I agree as well. We already have a partial solution for DC where implementations are using IPv6 ND RA messages to ascertain the link-local address on P2P fabric addresses. The BGP speakers then peer on the link-local addresses. RFC 5549 is then used for IPv4 routes. Of course, we can do a lot better than that.
Thanks,
Acee

From: Bgp-autoconf <bgp-autoconf-bounces@ietf.org> on behalf of Jeff Tantsura <jefftant.ietf@gmail.com>
Date: Saturday, February 1, 2020 at 11:45 AM
To: Jie Dong <jie.dong@huawei.com>
Cc: "bgp-autoconf@ietf.org" <bgp-autoconf@ietf.org>, Robert Raszuk <robert@raszuk.net>
Subject: Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BGP Auto Session Setup

+1
Regards,
Jeff


On Jan 31, 2020, at 22:17, Dongjie (Jimmy) <jie.dong@huawei.com> wrote:
Hi Robert and Jeff,

Yes I also think we’ve agreed to treat them separately. Then the next question is which scenario(s) would be the first target for this design team? My personal feeling is there may be more interests to work on the DC case first. What do you think?

Best regards,
Jie

From: Bgp-autoconf [mailto:bgp-autoconf-bounces@ietf.org] On Behalf Of Robert Raszuk
Sent: Thursday, January 30, 2020 8:14 PM
To: Jeff Tantsura <jefftant.ietf@gmail.com>
Cc: bgp-autoconf@ietf.org
Subject: Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BGP Auto Session Setup

Cool - then we accomplished first design team milestone :)

On Thu, Jan 30, 2020 at 1:12 PM Jeff Tantsura <jefftant.ietf@gmail.com<mailto:jefftant.ietf@gmail.com>> wrote:
A statement with a question mark ;-)
To rephrase - I think we have already agreed.

Regards,
Jeff

> On Jan 30, 2020, at 13:08, Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>> wrote:
>
>
>
> >  To my feeling we have already agreed to treat them separately?
>
> Is that a question or a statement ?
>
>
>