Fwd: [Panrg] Proposed Path Aware Networking RG

"Alvaro Retana (aretana)" <aretana@cisco.com> Wed, 12 July 2017 16:39 UTC

Return-Path: <aretana@cisco.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66A70120721 for <routing-discussion@ietfa.amsl.com>; Wed, 12 Jul 2017 09:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 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.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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
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 OZttsu1JMlCM for <routing-discussion@ietfa.amsl.com>; Wed, 12 Jul 2017 09:39:54 -0700 (PDT)
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 2D82A128B8F for <routing-discussion@ietf.org>; Wed, 12 Jul 2017 09:39:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10160; q=dns/txt; s=iport; t=1499877594; x=1501087194; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=Hw1hJwqZps6V+0emrOYfFoyt44p2jx9DVih0a4A9jT0=; b=Mj8edMwEmOvq65+pY2PU1sm4hR20n+WUGVtUx7tZa0qIb4m05S7mbCdp VKvkRwMmJK+T/l62lFSyMCUkcesoZiF58j+Q7L4/MN9Ot2BdCeoFU9zLG eyBlr9u7PgPHGDsFBJlqZtnbU+DG7VvcpVXiDZiD3wG/9DGKhQCDriOkP I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DTAADgT2ZZ/51dJa1dGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBg1pkgRSOCZFwkFeFLIIRIQEKhUoCg1E/GAECAQEBAQEBAWsdC4UYAQI?= =?us-ascii?q?BAwEBZQEGBBcCARkBAgECKAcnCxQDBAIIAgQTFIk3ZBCvaIsiAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBGAWDKINNgWErgnmERkQWgw2CMQWHIpAah2wCh0aDR4NHhTm?= =?us-ascii?q?CDIVLik6VUAEfOIEKdRVJEgGHAgF2hhqCPwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.40,350,1496102400"; d="scan'208,217";a="269192490"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jul 2017 16:39:53 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id v6CGdrsr002802 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <routing-discussion@ietf.org>; Wed, 12 Jul 2017 16:39:53 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 12 Jul 2017 11:39:52 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Wed, 12 Jul 2017 11:39:52 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Subject: Fwd: [Panrg] Proposed Path Aware Networking RG
Thread-Topic: [Panrg] Proposed Path Aware Networking RG
Thread-Index: AQHS+tcq0M5MiT0e+0qSEB1fBLqBdaJQZUpT
Date: Wed, 12 Jul 2017 16:39:52 +0000
Message-ID: <D7E648F5-4F17-4D0C-803A-3561273F0DC2@cisco.com>
References: <AF3E6499-FAD2-4D3C-81D5-FACF32FA1DAE@trammell.ch>
In-Reply-To: <AF3E6499-FAD2-4D3C-81D5-FACF32FA1DAE@trammell.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_D7E648F54F174D0C803A3561273F0DC2ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/pgbdDK3LH-a2PLkSKpGAUBH-t6I>
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 16:39:56 -0000

FYI..

I believe there is a significant relationship to routing.

This Proposed RG is unfortunately scheduled against the ideas BOF, so I won't be able to attend.  For those not attending the ideas BOF, please make time for panrg.

Thanks!

Alvaro.

Thumb-typed and autocorrected..

Begin forwarded message:

From: "Brian Trammell (IETF)" <ietf@trammell.ch<mailto:ietf@trammell.ch>>
Date: July 12, 2017 at 2:21:47 AM EDT
To: tsv-area@ietf.org<mailto:tsv-area@ietf.org>
Cc: panrg@irtf.org<mailto:panrg@irtf.org>
Subject: [Panrg] Proposed Path Aware Networking RG

Greetings, all,

We'll be having a first meeting of the proposed Path Aware Networking (PAN) RG at IETF 99 in Prague next week, 13:30 Wednesday in Congress Hall 3. Since bringing path awareness to the endpoint has been the focus, at least in part, of a couple of running TSV working groups (MPTCP, TAPS), this RG seems to be of general interest to the transport area.  Olivier Bonaventure will give a review and overview of research to date in this space, and Adrian Perrig will present a fully path-aware Internet architecture, as an illustration of what is possible when path-awareness is promoted to a first-order goal.

>From our proposed charter (https://datatracker.ietf.org/group/panrg/about):

The Internet architecture assumes a division between the end-to-end
functionality of the transport layer and the properties of the path between the
endpoints. The path is assumed to be invisible, homogeneous, singular, with
dynamics solely determined by the connectivity of the endpoints and the Internet
control plane. Endpoints have very little information about the paths over which
their traffic is carried, and no control at all beyond the destination address.

Increased diversity in access networks, and ubiquitous mobile connectivity, have
made this architecture's assumptions about paths less tenable. Multipath
protocols taking advantage of this mobile connectivity begin to show us a way
forward, though: if endpoints cannot control the path, at least they can
determine the properties of the path by choosing among paths available to them.

This research group aims to support research in bringing path awareness to
transport and application layer protocols, and to bring research in this space
to the attention of the Internet engineering and protocol design community.

The scope of work within the RG includes, but is not strictly limited to:

- communication and discovery of information about the properties of a path on
local networks and in internetworks, exploration of trust and risk models
associated with this information, and algorithms for path selection at
endpoints based on this information.

- algorithms for making transport-layer scheduling decisions based on
information about path properties.

- algorithms for reconciling path selection at endpoints with widely deployed
routing protocols and network operations best practices.

The research group's scope overlaps with existing IETF and IRTF efforts, and
will collaborate with groups chartered to work on multipath transport protocols
(MPTCP, QUIC, TSVWG), congestion control in multiply-connected environments
(ICCRG), and alternate routing architectures (e.g. LISP), and is related to
the questions raised in the multiple recent BoF sessions that have addressed
path awareness and multiply-connected networks (e.g. SPUD, PLUS, BANANA).

he PAN(P)RG intends to meet at each IETF meeting until a
determination is made whether or not to charter it. Afterward, the RG intends to
meet at 1-3 IETF meetings per year, and hold one workshop per year, colocated
with a related academic conference.


_______________________________________________
Panrg mailing list
Panrg@irtf.org<mailto:Panrg@irtf.org>
https://www.irtf.org/mailman/listinfo/panrg