Hi Dino, Please see inline.
BR, Yihao -----Original Message----- From: Dino Farinacci <farina...@gmail.com> Sent: 2021年12月7日 23:44 To: Jiayihao <jiayi...@huawei.com> Cc: int-area@ietf.org Subject: Re: Side meeting follow-up: What exact features do we want from the Internet? > Thanks for clarification. > Then expectations of users intuitively from my side can be: > > (1) I want to be agnostic to the network protocols (I do not want to know > Bluetooth, ZigBee, thread, Airdrop, or any others). I just hope that if I buy > an IoT device, I can take control of it by my phone (better locally). That is correct. That is how IP was born in the days of Ethernet, Token Ring, FDDI, X.25, DDN-X.25, Frame Relay, SMDS, and ATM. Not to mention all the HDLC variant serial links. Bridging across these data links (at layer 2) was always problematic. > (2) I want to have strict privacy/security. No traces can be linked to me > according to the networking actions I took once I choose to remain anonymous. Meaning the IP layer encrypts ALL packets and source addresses are obfuscated and possibly randomized. The ideas and points Tom (and Luigi) has made in the past. > (3) I can access my devices/data anytime, anywhere, all under my control. Any > data that I have/bought cannot be confiscated or taken away from me. I think the lay Internet user already assumes this. And expects the same service as when they plug into an electrical outlet. If it doesn't work, they scream. [jiayihao] Here I mean our data is controlled by our service provider not user themselves. For example, if I bought a movie X from an online streaming provider A, I still do not own this movie X and have to pay again if I want to watch movie X from online streaming provider B. However, I am not that sure if it can be categorized to a network requirement. > (4) Similar to your first point: I want to be always attached to the Internet > by any personal devices. (then I can better enjoy the features above) Yes. > Here I have another question: application developer/programmer should have a > different angle for new features. Of course application developer/programmer > should to be agnostic (or learn as less as possible) to network stuffs during > developing, but definitely they have more insights and more details shall be > learned by them. App developers control user behavior by making their services/functionality available with good UI. Make it easy for the user to get do things with the fewest number of steps. A counter example is the Facebook iOS app. [jiayihao] Agree that App developers should not care about network stuff like the session continuity during device movement. However, App developers do learn things like URL, domain names, DNS, Quic, CDN, proxies.....,and make them transparent behind the good UI. So there do have some network stuffs that are agnostic to users but are not agnostic to App developers. [jiayihao] My observation is: If we consider network features/requirements from App developers, it will finally result in discussion about the network architecture. Dino _______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
