From 403ccb1f962d60ac22f8488899781006a87fc707 Mon Sep 17 00:00:00 2001 From: Brian Trammell Date: Tue, 12 Sep 2017 11:30:14 +0200 Subject: [PATCH] suggestions for section 8 --- draft-iab-marnew-report.md | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/draft-iab-marnew-report.md b/draft-iab-marnew-report.md index 70bce8b..1ff5eaf 100644 --- a/draft-iab-marnew-report.md +++ b/draft-iab-marnew-report.md @@ -109,8 +109,14 @@ informative: date: September 7, 2015 SPUD: - target: https://datatracker.ietf.org/wg/spud/documents/ - title: Session Protocol for User Datagrams + target: https://tools.ietf.org/html/draft-trammell-spud-req-04 + title: Requirements for the design of a Session Protocol for User Datagrams (SPUD) + author: + ins: B. Trammell, M. Kuehlewind + + PLUS: + target: https://www.ietf.org/proceedings/96/plus.html + title: Proceedings of the PLUS BoF at IETF 96, Berlin, July 2016 CONEX: target: https://datatracker.ietf.org/wg/conex/documents/ @@ -296,7 +302,7 @@ Network or Transport Solution Sessions aimed to discuss suggested and new soluti Middleboxes in the network have a number of uses, some which are more beneficial than they are controversial. Collaboration between these network elements and the endpoints could bring about better content distribution. A number of suggestions were given, these included: - Mobile Throughput Guidance [MTG]: exchanges data between the network elements and the endpoints via TCP Options. It also allows for gaining a better idea of how the transport protocol behaves and improving user experience further, although the work still needs to evolve. -- SPUD [SPUD]: a UDP-based encapsulation protocol to allow explicit cooperation with middleboxes while using new, encrypted transport protocols. +- SPUD [SPUD]: a proposed, UDP-based encapsulation protocol to allow explicit cooperation with middleboxes while using new, encrypted transport protocols. - Network Status API: An API for operators to share congestion status or the state of a cell before an application starts sending data could allow applications to change their behaviour. - Traffic classification: classifying traffic and adding this as metadata for analysis throughout the network. This idea has trust and privacy implications. - ConEx [CONEX]: a mechanism where senders inform the network about the congestion encountered by previous packets on the same flow, in-band at the IP layer. @@ -397,11 +403,12 @@ Throughout the workshop attendees placed emphasis on the need for better collabo Since MaRNEW a number of activities have taken place in various seperate working groups or groups external to IETF. The ACCORD BoF was held at IETF95 which brough the workshop discussion to the wider IETF audiences by providing an account of the discussions within the workshop and highlighting key areas to progress on. Key areas to progress and an update on their current status follows: -* The collection of useable metrics and data were requested by a number of MaRNEW attendees, especially for use within the MAP Research Group; this has been difficult to collect due to the closed nature of mobile network operations. -* Understanding impacts to Stack Evolution has continued within the IAB's Stack Evolution programme and throughout Transport related working groups such as TSVWG. +* The collection of useable metrics and data were requested by a number of MaRNEW attendees; this has been difficult to collect due to the closed nature of mobile network operations. +* The IAB's Stack Evolution programme has continued discussion and development of guidance on the evolvability of protocols. +* The Measurement and Analysis of Protocols (MAP) Research Group was chartered before IETF 96, and provides a venue for the discussion of data and research on many of the topics addressed at MaRNEW, including the deployment of encryption and the prevalence of in-network inpairments to protocol evolution. * The Mobile Throughput Guidance draft has entered into a testing and data collection phase; although further advancements in transport technologies (noteably QUIC) may have stalled efforts in TCP-related proposals. * Attempts on proposals for caching of encrypted content continue albeit with some security flaws which proponents are working on further proposals to fix. Most often these are discussed within the HTTP WG. -* The PLUS working group forming BoF was unsuccessful with attendees expressing concern on the privacy issues associated with the data sharing possibilities of the shim layer proposed. +* Work on SPUD {{SPUD}} continued as the Path Layer UDP Substrate {{PLUS}}. A PLUS working-group forming BoF was held at IETF 96 in Berlin. A working group was not formed due largely to concerns about the potential end-user privacy impacts of a generic facility for endpoint-path signaling. The most rewarding output of MaRNEW is perhaps the most intangible. MaRNEW gave two rather divergent industry groups the opportunity to connect and discuss common technologies and issues affecting users and operations. Mobile Network providers and key internet engineers and experts have developed a greater collaborative relationship to aid development of further standards which work across networks in a secure manner.