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:37 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 C7BCB3A0EB1; Sun, 23 Feb 2020 12:37:33 -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=mJE91j4s; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=O+H3f/n9
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 loYkgu98M8LS; Sun, 23 Feb 2020 12:37:31 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69F983A0EB0; Sun, 23 Feb 2020 12:37:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=32435; q=dns/txt; s=iport; t=1582490251; x=1583699851; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=W5iJP6kgq/+yq1xUwOyvBVSx/VLw9OOluCTB0YI1GoQ=; b=mJE91j4sUwtZUNBbTNTB8Y20XyYjBFA2UL5uquC9owpf/njgYRp1oM+F OerTUj6H8XAMML1nxGS/18mZBetUlfC+65ogKQir2bojkeIJoD1fR8Q8c 6GikST4wwKxX8DluubTNuYAaev3S7xiX64tSiFNNjUVDaG2aUIFQTPtVm w=;
IronPort-PHdr: =?us-ascii?q?9a23=3AYbKiyxTO8k+FI405QyHnJ0BUEdpsv++ubAcI9p?= =?us-ascii?q?oqja5Pea2//pPkeVbS/uhpkESUANfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH1?= =?us-ascii?q?5NksAKh0olCc+BB1f8KavjZCE3NM9DT1RiuXq8NBsdFQ=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AbAQDS4VJe/51dJa1mGgEBAQEBAQE?= =?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYF7gSUvUAVsWCAECyqEFINGA4pvgjoliWOOMYF?= =?us-ascii?q?CgRADVAkBAQEMAQEYAQoKAgQBAYRAAheBdSQ4EwIDDQEBBQEBAQIBBQRthTc?= =?us-ascii?q?MhWMBAQEBAwEBEAYLHQEBJgYLAQ8CAQgRAwEBARYLBwMCAgIfBgsUCQgCBA4?= =?us-ascii?q?FGweDBAGBfU0DLgEOoSkCgTmIYnWBMoJ/AQEFgS8Bg0sNC4IMAwaBOIwkGoI?= =?us-ascii?q?AgTgMFIIeLj6CG0kBAQKBHA0FARECAUANCQmCUjKCLI4dgkiFcIoIjnlECoI?= =?us-ascii?q?8h1GHd4JnhDYcgkmIG5BKjX4LiWOCLpAdAgQCBAUCDgEBBYFpImdxcBU7KgG?= =?us-ascii?q?CQVAYDY4dDBcVgzuFFIVBdAKBJ41VAQE?=
X-IronPort-AV: E=Sophos;i="5.70,477,1574121600"; d="scan'208,217";a="435209078"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Feb 2020 20:37:30 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 01NKbUmj009600 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 23 Feb 2020 20:37:30 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 23 Feb 2020 14:37:29 -0600
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 23 Feb 2020 14:37:29 -0600
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Sun, 23 Feb 2020 15:37:28 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OpxWvzDGkvYBQjUNoImc1HJSndSljurh7nmP1xe1CDZkDz/3uxr49gGIlbuEBV7SEvYiudIYefFOl/aj9mF2FX9dh262+skSwRa1poqfjfltnVlDOiqUYk1kE1Ylpt4G7+yu2DQu2hQK8+kTo8G4FJ/0Ccr4JVg7yrN+H5hkIjNgdPdv6/dF0GTh+BhLuWdUNCfH+F6+lHp1ZoKRbBt5kXIX0oUqIh+NE9imLuU4kGyeq/m9i8EhwuOycuMoBYdjYUjpNNmpIsVRKIEQGebeRsp8J1/GBq+/5RLFX2WYCYb6PVVx6V7LaiIkRKUYIsHa+Oqxtxd5tlkCdvxiDLLNQg==
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=W5iJP6kgq/+yq1xUwOyvBVSx/VLw9OOluCTB0YI1GoQ=; b=N02D7jYpDjryZKfPIprSS8V7/tIM5mPK3CmkTpzQ1NRZCn7JUtZxuowhdfB7ZIBgW9xn652iFUgMUWYbPWH3yctfnwB+UxPNgkpZ1DL6Bqta4CBY2rcQRU4Fu9F5+qUxMIks5NPC1u6Bf7tbIYN/aqFriHCL8fTgD048QgIPsmii/GfSrZio5YhICE0YSsD+P+gFiNN5Xt8muTxnGskpBESK9bR2/IvgH7oK58l8dk6I0vl/E9v1lgAL0lcbBaQHpnZWA3f2DvCMjA4A8Z818tU9Ple+vof/4VY26eFuVT+IrZZh2NBVwGbm2tKYlSfNfkC+UBrgzYFqZMmSQG73Rg==
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=W5iJP6kgq/+yq1xUwOyvBVSx/VLw9OOluCTB0YI1GoQ=; b=O+H3f/n9gOTy8KfXB6GJsvyUI0OnDpxgPm0W1EqF8xQDz7z7NLESLIwdJ0kfcmG26/XG2RYbyywoOZFELBLUAlkQRGpOv6v47O57XXGXSpY5WPUhZAQ6CrW/PsCxqQ8w/5CnLqQIsuw4P+WuKH4xP9cO6dpA3mDXgUhGFVwN12k=
Received: from BN8PR11MB3794.namprd11.prod.outlook.com (2603:10b6:408:8f::13) by BN8PR11MB3681.namprd11.prod.outlook.com (2603:10b6:408:85::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2750.22; Sun, 23 Feb 2020 20:37:27 +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:37:27 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Jeff Tantsura <jefftant.ietf@gmail.com>
CC: "Dongjie (Jimmy)" <jie.dong@huawei.com>, Robert Raszuk <robert@raszuk.net>, "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/+bqxAgANLygCAAJWwgP//rRwA
Date: Sun, 23 Feb 2020 20:37:27 +0000
Message-ID: <CED47B1C-96DB-4978-907A-03B59A55B711@cisco.com>
References: <3311541C-7731-463B-91F5-7098731045CC@cisco.com> <8D380744-495F-4A8A-B986-E0A7FD58622B@gmail.com>
In-Reply-To: <8D380744-495F-4A8A-B986-E0A7FD58622B@gmail.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: dead516c-0f32-4332-fe2b-08d7b8a03273
x-ms-traffictypediagnostic: BN8PR11MB3681:
x-microsoft-antispam-prvs: <BN8PR11MB368158D32122B779CAE862E5C2EF0@BN8PR11MB3681.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)(346002)(366004)(136003)(376002)(39860400002)(189003)(199004)(54906003)(6512007)(316002)(71200400001)(81156014)(2906002)(6486002)(8936002)(81166006)(36756003)(8676002)(2616005)(33656002)(478600001)(5660300002)(53546011)(6506007)(66446008)(66476007)(66946007)(86362001)(76116006)(91956017)(66556008)(64756008)(6916009)(4326008)(966005)(186003); DIR:OUT; SFP:1101; SCL:1; SRVR:BN8PR11MB3681; 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: wC1ggrrmSmdhh30n3ibiO4VWFBD7G2ZupuCcZte3AJHBgToVNmRjXndBiXpPC4T8f8E56JbZz4LTkZQBQIGkJ6itZY6XE0Xa3aL01UiToC1Il5o5iIDc5Mju3i4hctmjS0OKQ+YAGC7EkPYEPjbnUQiOIQH3cxq53lW9QcTftEm/KD/h9ZEmSDZDbY7gy8VE/9tV1TPamQws2z+3iYwawwi1zJg6McvL7+pJLY/mbiAVuqpLAzrZgnjch0Q7KLtzIp0QMifXBU1ChFSWgIENV+bMg8q3CLNzeEmZPb5peG/YGwr+AxSdNCr4fOs7dHsEMRKvmO3cYtVPEhqBJlfw5Rq341UDbw7i6pdC39PVsBu643QAzNPdCHrUia1U+9Cg8yFlbs6wHcfozRhHCGa5mrTOaGobw9kkwbtgA83uuIsxZl2wjn1CkuP0ZE2t9zm4SSo08tE04Tcyyj5OQL3dfmGxDg8feLtWbAomQPRw6y+k7WxWFYbZHqM60Lfbb4yWUDT3Q8RhgryPSaIEo0gCdg==
x-ms-exchange-antispam-messagedata: fW6OwENmMa1VHfLrEvEmZHlWbqT2SCPrN8gIYVo5MmOkC4sdB03Pd1cNXfhyg8ZXppn+2OtjL5oCyJnT0HQlUsWqDVju59OIBln/BcbTbJlXapz29QlN//USz4h1/iiDuHb9KDVk+d9u4XzJXLGPc7BITdP4c3Kg0DTn4GHSXSg=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CED47B1C96DB4978907A03B59A55B711ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: dead516c-0f32-4332-fe2b-08d7b8a03273
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Feb 2020 20:37:27.4926 (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: kCGbyyNBZQtWEFNSmpBr9Tm3r4OQmdHlbkVCUmg7fo9HfLyWihFk+ZKwABNHaUHE
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR11MB3681
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/2IgGuaeHaFKmsJnuoJZMzM4qFdQ>
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:37:34 -0000

Jeff,

UTC +/- 8 confusion and not thinking where it has to be later…

Thanks,
Acee

From: Jeff Tantsura <jefftant.ietf@gmail.com>
Date: Sunday, February 23, 2020 at 3:34 PM
To: Acee Lindem <acee@cisco.com>
Cc: Jie Dong <jie.dong@huawei.com>om>, Robert Raszuk <robert@raszuk.net>et>, "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?

Acee,

6pm PST is 9pm EST, how did you get 1am?
Regards,
Jeff


On Feb 23, 2020, at 08:38, Acee Lindem (acee) <acee=40cisco.com@dmarc.ietf.org> wrote:
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 mailing list
Bgp-autoconf@ietf.org
https://www.ietf.org/mailman/listinfo/bgp-autoconf