[spring] IETF105 APN6 Side Meeting, Thursday Moring @Notre Dame Room
"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Wed, 17 July 2019 03:18 UTC
Return-Path: <pengshuping@huawei.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 5DFFE120058; Tue, 16 Jul 2019 20:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 nFbDoroMfCJ8; Tue, 16 Jul 2019 20:18:22 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 0D0B0120025; Tue, 16 Jul 2019 20:18:22 -0700 (PDT)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 6E52B1F8AE857E96B988; Wed, 17 Jul 2019 04:18:19 +0100 (IST)
Received: from DGGEML406-HUB.china.huawei.com (10.3.17.50) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 17 Jul 2019 04:18:18 +0100
Received: from DGGEML512-MBX.china.huawei.com ([169.254.2.81]) by dggeml406-hub.china.huawei.com ([10.3.17.50]) with mapi id 14.03.0439.000; Wed, 17 Jul 2019 11:18:06 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: 6man WG <ipv6@ietf.org>, "spring@ietf.org" <spring@ietf.org>
CC: Lizhenbin <lizhenbin@huawei.com>
Thread-Topic: IETF105 APN6 Side Meeting, Thursday Moring @Notre Dame Room
Thread-Index: AdU8Te1+jU2/RoO4TxyLTMKKuuE0Ow==
Date: Wed, 17 Jul 2019 03:18:05 +0000
Message-ID: <4278D47A901B3041A737953BAA078ADE1484A914@dggeml512-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.169.124]
Content-Type: multipart/alternative; boundary="_000_4278D47A901B3041A737953BAA078ADE1484A914dggeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/Lp1qeH6U4dJgBpG9CFBqtDiz9YM>
Subject: [spring] IETF105 APN6 Side Meeting, Thursday Moring @Notre Dame Room
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: Wed, 17 Jul 2019 03:18:24 -0000
Dear all, We are planning a Application-aware IPv6 Networking (APN6) Side meeting at this IETF Thursday morning @Notre Dame Room. Please find the meeting information (incl. Agenda) below and more details on the topic from the referenced drafts. As the Internet is progressing, the decoupling of applications and network transport causes the service provider network pipelined which becomes the bottleneck of the network service development. A multitude of applications are being carried over the IP network which have varying needs. However the network is hard to learn the applications' service requirements which cause it is difficult to provide truly fine-granular traffic operations for the applications and guarantee their SLA requirements. The Application-aware IPv6 Networking (APN6) is to make use of IPv6 extensions header to convey the application related information including its requirements along with the packet to the network so to facilitate the service deployment and network resources adjustment. We look forwards to your presence for a very productive discussion. https://trac.ietf.org/trac/ietf/meeting/wiki/105sidemeetings Room: Notre Dame - Thursday Occupancy: up to 50 attendees Configuration: classroom Location: Notre Dame<https://datatracker.ietf.org/meeting/105/floor-plan#2nd-floor> Meeting Name Area Contact Meeting Description More information 08:30 APN6 6man/spring Zhenbin Li APP-Aware IPv6/SRv6 Networking Tentative Agenda: 1. Problem Statement 2. Relevant IETF work * Application-aware IPv6 Networking * FAST: Firewall and Service Tickets * Path Segment * IFIT/IOAM * Detnet 1. Use cases 2. Discussions https://datatracker.ietf.org/doc/draft-li-cross-ietf-area-work/<https://datatracker.ietf.org/doc/draft-li-cross-ietf-area-work/> https://datatracker.ietf.org/doc/draft-li-6man-app-aware-ipv6-network/<https://datatracker.ietf.org/doc/draft-li-6man-app-aware-ipv6-network/> https://datatracker.ietf.org/doc/draft-li-6man-enhanced-extension-header/<https://datatracker.ietf.org/doc/draft-li-6man-enhanced-extension-header/> https://datatracker.ietf.org/doc/draft-li-6man-ipv6-sfc-ifit/<https://datatracker.ietf.org/doc/draft-li-6man-ipv6-sfc-ifit/> https://datatracker.ietf.org/doc/draft-li-6man-srv6-path-segment-encap/<https://datatracker.ietf.org/doc/draft-li-6man-srv6-path-segment-encap/> https://datatracker.ietf.org/doc/draft-geng-spring-srv6-for-detnet<https://datatracker.ietf.org/doc/draft-geng-spring-srv6-for-detnet> 09:45 NOT AVAILABLE NOT AVAILABLE NOT AVAILABLE NOT AVAILABLE NOT AVAILABLE Best regards, Shuping
- [spring] IETF105 APN6 Side Meeting, Thursday Mori… Pengshuping (Peng Shuping)
- Re: [spring] IETF105 APN6 Side Meeting, Thursday … Lizhenbin
- [spring] 答复: IETF105 APN6 Side Meeting, Thursday … Pengshuping (Peng Shuping)