IETF Logo Mail Archive

Re: [Bgp-autoconf] A conference call in next week to discuss BGP autoconf requirements?

"Mankamana Mishra (mankamis)" <mankamis@cisco.com> Fri, 21 February 2020 22:32 UTC

Return-Path: <mankamis@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 3E19A1201EA; Fri, 21 Feb 2020 14:32:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.497
X-Spam-Level:
X-Spam-Status: No, score=-14.497 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, URIBL_BLOCKED=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=QiLIltt3; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=rYaUTtpH
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 RkRhGZjkZ5qQ; Fri, 21 Feb 2020 14:32:17 -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 51CF912082C; Fri, 21 Feb 2020 14:32:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11901; q=dns/txt; s=iport; t=1582324337; x=1583533937; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=xtAeoFoG7QajZA+suR/7+xHCQyCCnmfDq+A10+rj/Cs=; b=QiLIltt3Y7KV00zzRWVcqJMPAwR8rYlIczKZjskhEDrWHP1/TExYQE0O MHIYbC4yM/9bYKphnYq4sjTCuAqnS9nBKTd3lTMtxBdNkHTa8iNmL2Wlm HCfsSlUXqQQcbqkyYZ0lZCLVeyH67Du/V7a3Ra+NlHo7PcKmT13nmvNpi g=;
IronPort-PHdr: =?us-ascii?q?9a23=3A+Hq8QB0rEHx/J15fsmDT+zVfbzU7u7jyIg8e44?= =?us-ascii?q?YmjLQLaKm44pD+JxKGt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSw?= =?us-ascii?q?dDjMwXmwI6B8vQDET9L/fvbjcSF8VZX1gj9Ha+YgBY?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AZAgD8WVBe/4ENJK1mHAEBAQEBBwE?= =?us-ascii?q?BEQEEBAEBgWoEAQELAYEkL1AFbFggBAsqCoQKg0YDinOCX5MyhGKBQoEQA1Q?= =?us-ascii?q?JAQEBDAEBGAEKCgIEAQGEQAIXgXUkNwYOAgMNAQEFAQEBAgEFBG2FNwyFZgE?= =?us-ascii?q?BAQEDAQEQER0BASYGCwEPAgEIEQMBAhYSAwICAiULFAkIAQEEAQ0FGweDBAG?= =?us-ascii?q?BfU0DLgEOoz0CgTmIYnWBMoJ/AQEFgS8BgRSCeBiCDAMGgTgBjCMagUE/gTg?= =?us-ascii?q?ggh4uPoJkAQGBHg0FARECAUANCQmCUjKCLI4dgkiFcJlFCoI8h1CHd4cdHIJ?= =?us-ascii?q?JiBuQSo1+C2eIfJJLAgQCBAUCDgEBBYFoI2dxcBU7KgGCQVAYDY4dOIM7hRS?= =?us-ascii?q?FQXSBKYxdAYEPAQE?=
X-IronPort-AV: E=Sophos;i="5.70,470,1574121600"; d="scan'208,217";a="729252453"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 21 Feb 2020 22:32:16 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id 01LMWGEE025628 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 21 Feb 2020 22:32:16 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 21 Feb 2020 16:32:15 -0600
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 21 Feb 2020 16:32:15 -0600
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 21 Feb 2020 16:32:15 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ROna5DX58Q7MunhXGqC21OVSe5GdbfmVJAOfs5A62yEEByrFhWZIn2Sj2pqokmJtiW1i4tJj9cczvcFkHMEmE53fnAYbP6Kd4qBXxpzEwjEnLvqkcd+ZN/M2ERnAyoAfslqrdVyK3+11XF79ADlQYDlIlFOJps4HkMk2OPrex/qQaxrLuVe6HGXlP+oD7M/xXaalfv/Kqk4gz+FSqnFfFhWFT4II3/YOyV+TN0smQ5Bc3o8kTvOftjAsc3ifm3ch2dow8+mLrmYJVhSriH58dNqzzeHRuKlz2k6hW8JNlNFST84Cf7L0tlEcR8vY/PrBpXJRZJ6j93hzeRfZk2G70A==
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=xtAeoFoG7QajZA+suR/7+xHCQyCCnmfDq+A10+rj/Cs=; b=ejC4whPjxh5Vi6JOgQY0fGbD4Tlja1CeBuH6lzdG+eOY2b4S4xgvhuwOfpCuzzPfrH51pdTpQkVH4M3HUBvSmApTxAaoNzxXZzaTs2HXzam98N4gF2MxpQrBGcQHCIeTkV0mvX/hLDXhncVGBd7T6a4YBqVetfJ1ZOyHW6qlR5pLP6da0syQMCHCvnbPLmdCLa+YSz2E0bsNit+aLdMh90cg66PJ9x3m0Kf6rixr+tu2wq7QOJgTy0jgvnO267BEGPraitYohwJVp860VL3sr/X8txV0MIG9q8k+aCDYtuQAi0o5LRLbwjOMV4g3ylfqa26QLodXq1ZmfqA+oyF3Nw==
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=xtAeoFoG7QajZA+suR/7+xHCQyCCnmfDq+A10+rj/Cs=; b=rYaUTtpH3xuQ0WdDTXXi2Z+bVx9NmTfXsDRJOQTAkmqIUcYgnDvh5Ou9deoz1UsXYHGJwI5uXp2Qt5QLTZYOLKbkmwJOcU3YMwLsqyLRaUJQ6uaI0f7pmcyatyUITZeu5OBfxaEUxwWD6ls8OI/lBPifkpCq2SGUMWau7RO6eks=
Received: from SN6PR11MB2654.namprd11.prod.outlook.com (2603:10b6:805:54::31) by SN6PR11MB3214.namprd11.prod.outlook.com (2603:10b6:805:c7::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2729.22; Fri, 21 Feb 2020 22:32:14 +0000
Received: from SN6PR11MB2654.namprd11.prod.outlook.com ([fe80::49af:e9cb:d3fe:55c2]) by SN6PR11MB2654.namprd11.prod.outlook.com ([fe80::49af:e9cb:d3fe:55c2%3]) with mapi id 15.20.2729.033; Fri, 21 Feb 2020 22:32:14 +0000
From: "Mankamana Mishra (mankamis)" <mankamis@cisco.com>
To: Robert Raszuk <robert@raszuk.net>, "Dongjie (Jimmy)" <jie.dong@huawei.com>
CC: "bgp-autoconf@ietf.org" <bgp-autoconf@ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>
Thread-Topic: [Bgp-autoconf] A conference call in next week to discuss BGP autoconf requirements?
Thread-Index: AdXoneGeq7UxQ91YQV2Dhzv5vvtPdwAZ1ImA//99AQA=
Date: Fri, 21 Feb 2020 22:32:13 +0000
Message-ID: <10B94B2F-D680-441E-87C1-4F6A29E81BD2@cisco.com>
References: <70e313e9faec408b85c6b29cff0be23f@huawei.com> <CAOj+MMG2wLNf-1sD+RbTCxocFsPViASr47vy-6TZCeFOhjTSmw@mail.gmail.com>
In-Reply-To: <CAOj+MMG2wLNf-1sD+RbTCxocFsPViASr47vy-6TZCeFOhjTSmw@mail.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=mankamis@cisco.com;
x-originating-ip: [128.107.241.176]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 58387e3e-6b47-401e-3793-08d7b71de633
x-ms-traffictypediagnostic: SN6PR11MB3214:
x-microsoft-antispam-prvs: <SN6PR11MB3214A8D82FD37E7DCA84237FDF120@SN6PR11MB3214.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0320B28BE1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(346002)(376002)(366004)(396003)(39860400002)(199004)(189003)(81156014)(8676002)(64756008)(71200400001)(66446008)(8936002)(66476007)(66556008)(4326008)(2616005)(36756003)(2906002)(81166006)(478600001)(6486002)(5660300002)(26005)(33656002)(966005)(86362001)(316002)(76116006)(91956017)(6512007)(110136005)(53546011)(54906003)(66946007)(186003)(6506007); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB3214; H:SN6PR11MB2654.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: mk+xyrRDzZMLE4ZPjwnED+MZCl/qGKq6tlBAlK7fHSnUKTjEuCCXzlvAS0zldfDA3unbkceEMIn+OYnVUcWk8PwKpLNkd5KeCGxe7paZsC1OcmrUb0uu1r1NfrKchdO8Z7cgM4uRCFygPt8/cZWaRqQuZCYSipGn52kHgnYlZ1AYlPC//qJ3s382uqyhBzfjfbBGJeauchOqn3k5lIhL419mzWBQalRvczxQAIlReTyybfeddSMhcHBhZxXleC/SmiJePf7xe20vb5IBSO8/sT+sMSCrU3fdTOE9Br5xK1YGcgmZbYPPGBY14D/LrQ6hBb+uENL562IICQ8ODOmoKsufj0TfAUQpT+BiroUKwABgRix1gI1kygY/i39+zeECkKnjXoJHH9t2lymr/eA+zDjFHYLk7wtg3DJD7LykcuMPd2HS3GDSwZfLDa2AXQczEPcsypuURaA/P6AbMjZHa71dJGb5GcXWSBzRC2+2Pa8dWKaZlzazu39YoqqSbHEFs1SbSPj803UwXGxnRt4RMg==
x-ms-exchange-antispam-messagedata: 68d3klO+QhhFKlezJ8iJdQZBQgI6BH5pn9dquDKq9AerRXd+6d4nA41nEUC86UEC1zjqea17cpY40hpLkd1iV/6RscXSgI4bC9wiXW0ml/D+RJGJj//+mVi4SJQGrAtEhs/bsgOC08jlUf/Nk4BbCg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_10B94B2FD680441E87C14F6A29E81BD2ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 58387e3e-6b47-401e-3793-08d7b71de633
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Feb 2020 22:32:13.8666 (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: GLwoU/uV6tPb865wQ4AzwalwyAcTL3ZGxIKHxejdWMP3j09qFwD+24tE6NGmVYyrfIULbqHMyHEoOt/X+xE9dg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR11MB3214
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/es8rf8M1HEtagex6aWVrHYgDAHQ>
Subject: Re: [Bgp-autoconf] A conference call in next week to discuss BGP autoconf requirements?
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: Fri, 21 Feb 2020 22:32:27 -0000

I don’t doodle link working to select time.

From: Bgp-autoconf <bgp-autoconf-bounces@ietf.org> on behalf of Robert Raszuk <robert@raszuk.net>
Date: Friday, February 21, 2020 at 2:21 PM
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>
Cc: "bgp-autoconf@ietf.org" <bgp-autoconf@ietf.org>rg>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>
Subject: Re: [Bgp-autoconf] A conference call in next week to discuss BGP autoconf requirements?

May we have it 8:00-15:00 PST instead ?

Also what can't be discussed over email ?

Thx,
R.

On Fri, Feb 21, 2020 at 11:06 AM Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>> wrote:
Dear all,

The IETF 107 meeting is approaching, we need to make more progress to reach consensus on the requirements (for the DC case first), then we could review the candidate solutions about how they match the requirements.

Based on the current mail list activity, it seems a conference call may help us to have more efficient discussion. Thus I’d suggest we arrange a 1-hour conference call in next week. I assume many of our team members are located in (UTC+8) and (UTC-8), thus a possible meeting time could be the 9:00 (UTC+8), which is 17:00 (UTC-8) in the previous day.

Here is the doodle poll for the meeting time, I also added other potential time slots, please respond to it by end of this weekend, thanks.

https://doodle.com/poll/6de9ei4iuubxs9ya

Once the meeting time is determined, we also need some help to setup the meeting. I’m not sure whether we could use the WGs Webex account for the design team conference call, will check with the chairs. If not, I’d appreciate if someone could help with this. Thanks in advance.

Best regards,
Jie
--
Bgp-autoconf mailing list
Bgp-autoconf@ietf.org<mailto:Bgp-autoconf@ietf.org>
https://www.ietf.org/mailman/listinfo/bgp-autoconf

v2.8.7 | Report a Bug | By Email