Re: [spring] Agenda for IETF 105 Published

Linda Dunbar <linda.dunbar@futurewei.com> Mon, 15 July 2019 20:31 UTC

Return-Path: <linda.dunbar@futurewei.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3264D12007C for <spring@ietfa.amsl.com>; Mon, 15 Jul 2019 13:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 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, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 b4ol2YMAIwTS for <spring@ietfa.amsl.com>; Mon, 15 Jul 2019 13:31:12 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-eopbgr800130.outbound.protection.outlook.com [40.107.80.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E942C120106 for <spring@ietf.org>; Mon, 15 Jul 2019 13:31:11 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dZ7YP3lxs2WWTiT6lhhgfXTpa4dY8hlaWrjbciMiAJpIKbZ8gDWXS2lGOmsfeQ7V25rvOI4oOTj7NmLLHH53/XtEOOgweZ+/Mn//K/i2m7dE5KR1aJcCIZyNLeCXtDr4iL6v1lm6+ZHb2yJLWazdI/4T/ZpV+/Li3PG+qV9kqUSxR68NUd5uYezgO+ssD8+JIF0FpGUQIdvLzCxJza7oGtF4OUBrmfBwy6eseBgdFepW9koVPcIMvOZZH3OGSfAs9l9ojsV+olbmP6bUFEXZPHT/JkfG2tER2GWfYAdtgf+/q2DATlDgtQKfms9Yk+19SPj+g6V9nDO7IWEnxfOzkA==
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=x9htpA/KNanQlnCu1vSfskuhzxEytxW6CdSCt8NK9ww=; b=mGw0nqe8Swk/DYJl2zRXGNa4AMNh1h21WO3jhmK1CuCJq337vjByw0KqAvyEnnAg5I3Lt5QeknDVd2LcFkULGa+a5ayiOVVn6paXlrVnmi52e4GjiNfM2kflGmYJkmupwm0Ko2pL+zZ5RpeRShE/1VHOa/+38fHNK9stIOde6eKZyBTlHsdZWfckA9xQ9JHwDV1zwGC3UYIIFkmmD181wJNqj3ajI9AS90TmsfjjZE15P4FSfPpC2fTT2OcLpT59n8nCZATPJybTChWBJ9RJeln8NkimaTyE9damoIjVCtNKRAiCvFX2XUoe/5Vzec3CMK9pqQF9oxJEbaoA5EIO6Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=futurewei.com;dmarc=pass action=none header.from=futurewei.com;dkim=pass header.d=futurewei.com;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=x9htpA/KNanQlnCu1vSfskuhzxEytxW6CdSCt8NK9ww=; b=biCkks285MTS7Rmth25NRrMxqUrrckWKXzJfj3prZAnycgHHuFT53vyR5ZEViU0Dxqe+1HmHcOaBAbQxubgZRzYfEtzErnZBH8zQIxTAwptunux/sk/8JPqD51FQIh2H+yZcFYjb6D3v8wOZ+gw/CHTRa5DLta6GF3pf2bij0hg=
Received: from MN2PR13MB3582.namprd13.prod.outlook.com (10.255.238.139) by MN2PR13MB3053.namprd13.prod.outlook.com (10.255.181.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.8; Mon, 15 Jul 2019 20:31:10 +0000
Received: from MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::e068:8461:62d7:e0c1]) by MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::e068:8461:62d7:e0c1%7]) with mapi id 15.20.2094.009; Mon, 15 Jul 2019 20:31:10 +0000
From: Linda Dunbar <linda.dunbar@futurewei.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, SPRING WG List <spring@ietf.org>
Thread-Topic: [spring] Agenda for IETF 105 Published
Thread-Index: AQHVN/6ts2KreC9R0UKe12vTdooMlqbMG+WAgAAL1cA=
Date: Mon, 15 Jul 2019 20:31:10 +0000
Message-ID: <MN2PR13MB35825286ABA77FEF0462038585CF0@MN2PR13MB3582.namprd13.prod.outlook.com>
References: <CAHd-QWuPiFtHT6TZ3G_O6ec9R16j+yg9LPVZGq-VPyoiu1nmHg@mail.gmail.com> <9715_1563219968_5D2CD800_9715_412_1_53C29892C857584299CBF5D05346208A48B83FF1@OPEXCNORM4D.corporate.adroot.infra.ftgroup>
In-Reply-To: <9715_1563219968_5D2CD800_9715_412_1_53C29892C857584299CBF5D05346208A48B83FF1@OPEXCNORM4D.corporate.adroot.infra.ftgroup>
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=linda.dunbar@futurewei.com;
x-originating-ip: [12.111.81.80]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 20fb2576-8a23-4186-0a2e-08d709635f6f
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR13MB3053;
x-ms-traffictypediagnostic: MN2PR13MB3053:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <MN2PR13MB305343B594C232F31D8CC03985CF0@MN2PR13MB3053.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 00997889E7
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(346002)(39840400004)(376002)(396003)(366004)(136003)(199004)(189003)(76116006)(66946007)(66066001)(33656002)(66476007)(14454004)(66556008)(5024004)(25786009)(256004)(6116002)(26005)(790700001)(3846002)(2906002)(966005)(6246003)(478600001)(8676002)(5660300002)(66574012)(99286004)(606006)(7736002)(2501003)(14444005)(8936002)(81156014)(71200400001)(71190400001)(236005)(110136005)(55016002)(486006)(316002)(81166006)(11346002)(44832011)(476003)(229853002)(64756008)(66446008)(76176011)(186003)(6506007)(53546011)(6436002)(52536014)(102836004)(7696005)(68736007)(9686003)(54896002)(446003)(53936002)(74316002)(86362001)(6306002); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR13MB3053; H:MN2PR13MB3582.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 6DQmZIhXrtgnwNkYiEjuVA6gsqce4/5IFGaTU7+6noe7DMpOx8d8/Cf2RhI0TNb98VY8gs//zbsForAxWTcE/ngyKyX9cLDkpDqHhtW5smDCjUwhrvrjR1PoTNd4I+UQGzKRlDZnqAN96tkLWh6QidIaetuQgR5Yaqgpg6YMOPU6h4R6DOlk3WDBFDp2BfdMkXpR8Sq3Kq6KuwUR+6sxH4gSygzOHvnExrvigzHqU1Ji6TPIJ4XB5t36ilikIDl7C9ysP4sWdgNmYsqT/+E+ysVWaK4kiR76jEuHmGbFXoKRj/QZoRWh6gRjAcZw52j319Taz7SUUkbnmiHNpMVQyYwMUt/5EtJokpgU19jHUVZr5XeOL2cvW5PuVVh95VMc0K9NSnQbjX18CsOblGMxHqq+F+YIbvu3iWlv0r2tJ3E=
Content-Type: multipart/alternative; boundary="_000_MN2PR13MB35825286ABA77FEF0462038585CF0MN2PR13MB3582namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 20fb2576-8a23-4186-0a2e-08d709635f6f
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jul 2019 20:31:10.2710 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ldunbar@futurewei.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB3053
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/gpsqta7Va4h3J0eVReJ-r7AP78E>
Subject: Re: [spring] Agenda for IETF 105 Published
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jul 2019 20:31:15 -0000

Bruno,

Why SPRING not request more time for IETF105?
SPRING had more time request than the WG session in IETF104. It happens again for IETF105.
Many WGs have multiple sessions, e.g. IDR has 3 sessions in IETF105; RTGwg has 2 sessions in IETF105, etc.

Linda Dunbar


From: spring [mailto:spring-bounces@ietf.org] On Behalf Of Rob Shakir
Sent: Thursday, July 11, 2019 5:38 PM
To: SPRING WG List
Subject: [spring] Agenda for IETF 105 Published

Hi SPRING WG,

Bruno and I have published the agenda for IETF 105 -- please see https://datatracker.ietf.org/doc/agenda-105-spring/<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fagenda-105-spring%2F&data=02%7C01%7Clinda.dunbar%40futurewei.com%7C6455eb609f084be7e91908d7095d1bfc%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C636988167826701223&sdata=eHT5FQDQxIngMYuXzrLjXSr0QRvA47Vt86h4szbe9W0%3D&reserved=0> for details.

Once again, we were vastly oversubscribed for time in this meeting - with almost 5 hours of requests for a 2 hour meeting. Most of these requests are for documents that are not discussed on the mailing list, and many of them are for new work. This makes the job of making sure that we have productive time face-to-face as a working group very difficult for the chairs. This is something that Bruno and I are discussing, and will aim to cover during our short slot at the beginning of the agenda.

To make sure that our meeting is as productive as possible:
·        if you're a WG participant: please read the drafts before the meeting,
·        if you're presenting: please avoid giving detailed overviews of the content of your document, and focus on outstanding open technical issues, or questions that you have for the SPRING working group.
If you have been allocated time, please send your slides by Monday July 22nd, at 10:00 EST. Slides that are received after this time may not be included in the meeting materials.

If you were not allocated time, please use this as a gentle shove to discuss your draft on the mailing list.

We look forward to meeting in Montréal.

Safe travels,
Bruno and Rob.



_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.