[Marnew] Marnew reflections

[Benoit Claise <[e-mail]>]

Dear all,

With a long flight, I've been having some time to think about MARNEW, 
and read some papers.
So here is a list of questions and reflections in preparation for the 
workshop.

- My first point is: what is specific to radio networks? 
Fluctuating/unknown bandwidth, limited cellular capacity, maybe more 
caching? IMO, the problem space is not specific to radio networks, 
specifically if we have QoE in mind. We can think of it as "Managing 
Networks in an Encrypted World". I would be happy to learn about the 
radio network specifics during the workshop.

- Clarifying question: Is this workshop focusing on encrypted web 
traffic only, or all traffic/applications encryption?

- IMO, there are three aspects to encryption:
1. As an end user, I want privacy
2. As an employee, I require privacy, but I also require the right QoE 
for my business applications
3. As an operator, I'm not interested to look at the unencrypted 
packets, but I need to manage the networks. Everybody blames the network 
(even if it's not the network, but the servers ... but that's a 
different story). One aspect to provide the right QoE/QoS has been DPI. 
With the increase of encryption, that will not be a solution any longer.

- In terms of mechanism to provide the right QoS/QoE, there are two ways:
1. the operator is able to deduce the information. This is the DPI 
story. With encryption, that will be a challenge as mentioned.
2. the end-user communicate its QoS requirements to the network. Ex: hey 
mister operator, treat this series of packets (and I won't tell the 
content) as real-time traffic.

- Here we have a series of questions wrt the end-user communicating its 
requirements to the network.
     - QoE/QoS per device, per user, per session, per flow, per 
applications? Per application I guess, potentially per flow.
     - Do the end users know what they need in terms of QoS parameters: 
delay, packet loss, delay variation? Not sure...
       Maybe the applications know, but won't they all the time require 
the best QoS
     - DSCP has not been used appropriately. Why would it work this 
time? We could link this to some dollars: hey mister operator, treat 
this series of packets as real-time traffic, and I will pay extra for 
this. However, a complex billing system is ... costly.

- All these problems were discussed part of Application Enabled 
Collaborative Network (AECON).
However, that BoF was not approved at IETF 90. See 
http://trac.tools.ietf.org/bof/trac/wiki/BofIETF90 and review the 
description. There are some similarities.

Regards, Benoit