Re: [Bgp-autoconf] A conference call in next week to discuss BGP autoconf requirements?
"Acee Lindem (acee)" <acee@cisco.com> Sun, 23 February 2020 20:16 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 A13FB3A0E3F;
Sun, 23 Feb 2020 12:16:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level:
X-Spam-Status: No, score=-9.599 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=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=lwRITBd4;
dkim=pass (1024-bit key)
header.d=cisco.onmicrosoft.com header.b=NYZ2e3Dl
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 lc5g3qbwsD1o; Sun, 23 Feb 2020 12:16:47 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92])
(using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 7C38B3A0E3E;
Sun, 23 Feb 2020 12:16:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
d=cisco.com; i=@cisco.com; l=30179; q=dns/txt;
s=iport; t=1582489007; x=1583698607;
h=from:to:cc:subject:date:message-id:references:
in-reply-to:mime-version;
bh=h7G+CoEF439rwPhjoHB74p0if+fCXTRt8wnt3DBsn1g=;
b=lwRITBd4TjA8PYdG39c9dPpHQ+7ggICIMMyLgnHHUYsZ/l+T6UlOOxvz
hYpIhVrZYyL5MZDEkCpZjJU7LTuRQw5oY4DXjyr5/Uph2AfuhD7W7Bjhe
K6SFLFXnyhA5GJqpKTE21R+Av1z2T8DNBAuwSDWTitC8zpbX157ytVt22 A=;
IronPort-PHdr: =?us-ascii?q?9a23=3AsISohhZ7lTTyw1vHOnol74H/LSx94ef9IxIV55?=
=?us-ascii?q?w7irlHbqWk+dH4MVfC4el20QKbRp3VvvRDjeee87vtX2AN+96giDgDa9QNHw?=
=?us-ascii?q?QAld1QmgUhBMCfDkiuJfXnYgQxHd9JUxlu+HToeUU=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0APAQBy3FJe/4ENJK1mGgEBAQEBAQE?=
=?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYF7gSUvUAVsWCAECyqEFINGA4pwgl+YFIFCgRA?=
=?us-ascii?q?DVAkBAQEMAQEYAQoKAgQBAYRAAheBdSQ4EwIDDQEBBQEBAQIBBQRthTcMhWM?=
=?us-ascii?q?BAQEBAwEBEAYLHQEBJgYLAQ8CAQgRAwEBARYLBwMCAgIlCxQJCAIEAQ0FGwe?=
=?us-ascii?q?DBAGBfU0DLgEOoScCgTmIYnWBMoJ/AQEFgS8BgRSCNxiCDAMGgTiMJBqCAIE?=
=?us-ascii?q?4IIIeLj6CZAEBgR4NBQERAgFADQkJglIygiyOHYJIhXCKCI89CoI8h1GHd4c?=
=?us-ascii?q?dHIJJiBuQSo1+C2eIfJJLAgQCBAUCDgEBBYFpImdxcBU7KgGCQVAYDY4dOIM?=
=?us-ascii?q?7hRSFQXSBKY1VAQE?=
X-IronPort-AV: E=Sophos;i="5.70,477,1574121600";
d="scan'208,217";a="443207467"
Received: from alln-core-9.cisco.com ([173.36.13.129])
by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA;
23 Feb 2020 20:16:46 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15])
by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id 01NKGkKL024608
(version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL);
Sun, 23 Feb 2020 20:16:46 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-RCD-005.cisco.com
(173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3;
Sun, 23 Feb 2020 14:16:45 -0600
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-aln-001.cisco.com
(173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3;
Sun, 23 Feb 2020 14:16:45 -0600
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (64.101.32.56) by
xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server
(TLS) id
15.0.1473.3 via Frontend Transport; Sun, 23 Feb 2020 15:16:45 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
b=LF2egZuLlZhKFz6jPvYbT3Z3W1haFOVD7ND+gBboVordiFiazgVNjMlFQ0kDWlbeF8C3+PvcQAqHrTL83Wdg05pU0iGN6Q2ibi5Ofo9z88KDQ7e8bBQv5shCgarDpENzmEAYgvEbr5ekSt64AyL/e6TnNNfdyiCoeRdIoo/1ReCsoLCgl7qICvljsrh/M7bY+SrGXYBQWOQlw535Jfn2tw0Hu2tsXx7jjI+KMoRS0gnMn1w5ZQKNqJS5SRh2osdhLgi+j/0v37Vx9yV5cVCzcnJybb9BE0+7GN7RG3rYyxobunih9ALKSjBziaPD9FuRIOuDhP5i7KrucohuPaGaCg==
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=h7G+CoEF439rwPhjoHB74p0if+fCXTRt8wnt3DBsn1g=;
b=TKKEpmJhmEe8LkC3gJr8qQPRckZyNVdeIdCULQ+q3oxvUJvH1C/roVlkYM/+l+HqukgFm7hCQMGSrplLpI/pJ8qiYMQhMc/eHgsR0r86lEjqDdcKqCf8ZJJWFj6UCuSaSWQVUC/RpG3RH57gkjvbmUNxLGasxge6yAMmluuS/iJ66p9SAmWJxJbhBPqBmvcnEYk+2ZY4fTbjSogYUKsn1FZ/3OuMoUXIPt+c+oTOFeyVcxIAF3WjPvmM7ogEBQVXZgKmny1Oj3gB0T1dYCXZZqRB5toNA+1wt48dMqi71vgY4+TSMC61ia1zZkwafKC/0U8RlVUla3J10/3btzHp1Q==
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=h7G+CoEF439rwPhjoHB74p0if+fCXTRt8wnt3DBsn1g=;
b=NYZ2e3Dlcclmc23zbUnRb3GR0/HQegcUSdrytu2BP8+NPOedpUkBKLtgPQP9qqz0OigahYMk2F50oNyVcNphrmL2hyLy2mEwIbGrHo+EvdxujBdv02BR99XIDuNiiHtqv0+xHEC7yTKFWHJH1kH5LK2L5c8znpaSthP8FgWywIE=
Received: from BN8PR11MB3794.namprd11.prod.outlook.com (2603:10b6:408:8f::13)
by BN8PR11MB3601.namprd11.prod.outlook.com (2603:10b6:408:84::23)
with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2750.21; Sun, 23 Feb
2020 20:16:43 +0000
Received: from BN8PR11MB3794.namprd11.prod.outlook.com
([fe80::d939:a6fb:475:cddd]) by BN8PR11MB3794.namprd11.prod.outlook.com
([fe80::d939:a6fb:475:cddd%4]) with mapi id 15.20.2750.021; Sun, 23 Feb 2020
20:16:43 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>, Robert Raszuk <robert@raszuk.net>
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: AdXoneGeq7UxQ91YQV2Dhzv5vvtPdwAJEQGAADICOoD//6ytAP/+bqxAgANLygCAAD0CgA==
Date: Sun, 23 Feb 2020 20:16:43 +0000
Message-ID: <A45CF8F1-EEA3-48C6-9CA2-E19E05071127@cisco.com>
References: <70e313e9faec408b85c6b29cff0be23f@huawei.com>
<CAOj+MMG2wLNf-1sD+RbTCxocFsPViASr47vy-6TZCeFOhjTSmw@mail.gmail.com>
<a674af06587440d4b2143961084680cd@huawei.com>
<CAOj+MMFhbXOUmEnQs7WHJWAhkY3A--KVs3sUM4jHu9sMTEQznw@mail.gmail.com>
<d29ee4053a8046049381874b6aa28134@huawei.com>
<3311541C-7731-463B-91F5-7098731045CC@cisco.com>
In-Reply-To: <3311541C-7731-463B-91F5-7098731045CC@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.22.0.200209
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [2001:420:c0c4:1001::4b]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 12f55418-5937-4d03-8843-08d7b89d4d26
x-ms-traffictypediagnostic: BN8PR11MB3601:
x-microsoft-antispam-prvs: <BN8PR11MB3601A74A7B650BFEFAF8FAE6C2EF0@BN8PR11MB3601.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0322B4EDE1
x-forefront-antispam-report: SFV:NSPM;
SFS:(10009020)(4636009)(396003)(136003)(346002)(39860400002)(376002)(366004)(189003)(199004)(6506007)(53546011)(4326008)(6486002)(76116006)(86362001)(186003)(91956017)(66446008)(66476007)(66556008)(64756008)(66946007)(5660300002)(71200400001)(6512007)(478600001)(81166006)(8676002)(81156014)(966005)(8936002)(2616005)(2906002)(316002)(110136005)(54906003)(33656002)(36756003);
DIR:OUT; SFP:1101; SCL:1; SRVR:BN8PR11MB3601;
H:BN8PR11MB3794.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en;
PTR:InfoNoRecords; MX:1; A: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: wCYmTjH/AjjbJK2uz3VeFxfPv5AknaEqWPbZc/IHVKxiRmwm9AzA7mkBApBHU5o95AgQw+pHnBzUw+TKeSIuzslElv3aY4ukYiMA44mSksWlGV2wOn+GyqvkaUGuczV3qgrQDrmMO0Ruxvcfs40iW3LkhWESq/mwn9IuzKBkF5EbPBjpaUWK4UIbAjwz8EmBrDNUlOY6D9u+Zcvtw+i8i8YXSxGynBJmzYBZlUPO0xmYDjB12lYLnn0PmtHHd9dHYnP7LCeAOQy1/LWEDwYDCPcO5YDhwA7B2k2NWwor0BByZEr4sD/wrdk5eisHW6MnLxN27Hv/XFGUncCdZx1IsPaHf2akFPdLDJqDGirGCAZG1g7QKUbFmnNxoRGJBt+2iGrQfiDAeGZMwcZjm1wieakZfrPAD1ji9PerLIrqITiA95CGBG3ahRYlYy5Fipv2hrVp74L8xfYQHxqcvJCQ6qMH0CYfdGv+xPXjmPBW9A8MMOYWsLGvsJeArAfVkXKtyrH4PkrS2KAYmwADl8KdlA==
x-ms-exchange-antispam-messagedata: s7scEX+OPM0SaXCm0qKK76Px22z9jE3aYXwxAM63p4GfKjBvtfJEag1BFvgwIo/pDCIw4h2SyjudE+qXP1mPB5KB6w2xX4Je3Lh7hxdAO3zJl9CuZx68i2OFa5X9DnQAXynr16KGcm5aeXc9rr2SE9lOqK1Btw3uAH4mB95/+vw=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative;
boundary="_000_A45CF8F1EEA348C69CA2E19E05071127ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 12f55418-5937-4d03-8843-08d7b89d4d26
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Feb 2020 20:16:43.8752 (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: YtlzLFd/73i5UGbCP3tKmKLY5z/voJZeMOIFiBEe0whLogazpcZ1uy27QjqZVe6m
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR11MB3601
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/7N9kRB4oEz0pXyjTa3j8wUf5MRE>
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: Sun, 23 Feb 2020 20:16:50 -0000
Hi Jie, et al, Sue pointed out that I calculated the time wrong. It is 9:00 PM EST which is one of the times I expected. Thanks, Acee From: Acee Lindem <acee@cisco.com> Date: Sunday, February 23, 2020 at 11:38 AM To: Jie Dong <jie.dong@huawei.com>om>, Robert Raszuk <robert@raszuk.net> 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? That is 1 AM for Sue and I, not sure if I will attend. Please record. Thanks, Acee From: Bgp-autoconf <bgp-autoconf-bounces@ietf.org> on behalf of Jie Dong <jie.dong@huawei.com> Date: Sunday, February 23, 2020 at 9:17 AM To: Robert Raszuk <robert@raszuk.net> 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? Hi Robert, Sorry I thought you were also in N.A. While the doodle includes the morning time in Europe, the current survey shows most people chose the time slots which may not be convenient for European participants. According to the survey result, for the upcoming conference call we will choose February 24 18:00 (UTC-8), which is February 25 10:00 (UTC+8). For future meetings we could have another doodle poll if necessary. Sue, please help to set up the conference call, many thanks. Best regards, Jie From: Robert Raszuk [mailto:robert@raszuk.net] Sent: Sunday, February 23, 2020 1:15 AM To: Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>> Subject: Re: [Bgp-autoconf] A conference call in next week to discuss BGP autoconf requirements? Europe Thx, R. On Sat, Feb 22, 2020 at 3:23 PM Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>> wrote: Hi Robert, Thanks for your reply. 8:00-15:00 PST would be 24:00-7:00 Beijing time (the next day). I was trying to make the time acceptable to both Asia and N.A. participants. May I know which time zone are you in? The conference call proposal is just to speed up the design team discussion and hope to hear more opinions from the team members, everything could still be discussed on the mail list. Thanks. Best regards, Jie From: Robert Raszuk [mailto:robert@raszuk.net<mailto:robert@raszuk.net>] Sent: Saturday, February 22, 2020 6:21 AM To: Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>> Cc: bgp-autoconf@ietf.org<mailto:bgp-autoconf@ietf.org>; idr-chairs@ietf.org<mailto: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
- [Bgp-autoconf] A conference call in next week to … Dongjie (Jimmy)
- Re: [Bgp-autoconf] A conference call in next week… Susan Hares
- Re: [Bgp-autoconf] A conference call in next week… Robert Raszuk
- Re: [Bgp-autoconf] A conference call in next week… Mankamana Mishra (mankamis)
- Re: [Bgp-autoconf] A conference call in next week… Susan Hares
- Re: [Bgp-autoconf] A conference call in next week… Dongjie (Jimmy)
- Re: [Bgp-autoconf] A conference call in next week… Dongjie (Jimmy)
- Re: [Bgp-autoconf] A conference call in next week… Dongjie (Jimmy)
- Re: [Bgp-autoconf] A conference call in next week… Dongjie (Jimmy)
- Re: [Bgp-autoconf] A conference call in next week… Acee Lindem (acee)
- Re: [Bgp-autoconf] A conference call in next week… Acee Lindem (acee)
- Re: [Bgp-autoconf] A conference call in next week… Jeff Tantsura
- Re: [Bgp-autoconf] A conference call in next week… Acee Lindem (acee)
- Re: [Bgp-autoconf] A conference call in next week… Susan Hares
- Re: [Bgp-autoconf] A conference call in next week… Jeff Tantsura
- Re: [Bgp-autoconf] A conference call in next week… Robert Raszuk
- Re: [Bgp-autoconf] A conference call in next week… Dongjie (Jimmy)
- Re: [Bgp-autoconf] A conference call in next week… Robert Raszuk
- Re: [Bgp-autoconf] A conference call in next week… Dongjie (Jimmy)
- Re: [Bgp-autoconf] A conference call in next week… Susan Hares
- Re: [Bgp-autoconf] A conference call in next week… Randy Bush
- Re: [Bgp-autoconf] A conference call in next week… Robert Raszuk
- Re: [Bgp-autoconf] A conference call in next week… Randy Bush
- Re: [Bgp-autoconf] A conference call in next week… Robert Raszuk
- Re: [Bgp-autoconf] A conference call in next week… Randy Bush
- [Bgp-autoconf] 回复: A conference call in next week… 徐小虎(义先)