Comments & suggestions to draft-mm-wg-effect-encrypt-13

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Kathleen and Al,

 

Great draft! Captured the deep concerns of our customers (network service providers) of not being able to troubleshoot network issues and achieve better load balance when all traffic are encrypted.

 

But the network providers can’t really dictate how end points encrypt their traffic. Suggest add some description on how Network operators can have the options of using encapsulation (such as LISP, GENEVE, etc) at the network edges to carry all the information needed by the network operators for network maintenance or any other purposes.

 

With Net Neutrality almost being overturned, network service providers can provide more favorable services to the End Points that indicate the needed information from network operators, such as stream size, Latency Needs, etc.

Like your Section 6.3 Application Layer Protocol negotiation (ALPN). IMHO, the similar protocol should be expanded beyond TLS. IETF is a perfect position to specify those bits for end points to indicate to network, like the shim layer specified by PLUS initiative. Once the Shim Layer is specified, the End Points that need better service will be obligated to provide the information.

 

My two cents,

 

Linda Dunbar

 

 


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]