Re: [hybi] New port and Tunneling?

[Salvatore Loreto <[e-mail]>]

Hi Shelby,

this thread has been quite intense (45 mails, quite long mail, in less 
three days)


as chair I want to clarify that

- a P2P approach is not in scope of this wg (pleae read the charter and 
check what is really the focus of this wg: 
http://tools.ietf.org/wg/hybi/charters )

- the HTTP Upgrade handshake has been in the protocol proposal since the 
first version of the spec (before it become a wg item for HyBi wg),
   this wg has then decided that if the Handshake is based on Upgrade 
and then looks like HTTP, it needs to be HTTP but at same time have to take
   in consideration the security problem higlighted in the discussion.
   Instead of continuing to discuss theoretically about it, I have asked 
people to provide text for an HTTP Upgrade handshake that reflect the 
decision
   and the concerns of the wg.

- a TLS NPN approach as been proposed and several people, in the ml, 
have showed support for it.
   I have asked Adam to provide text describing/proposing an handshake 
solution using TLS/NPN
   he has kindly provided it in 
http://www.ietf.org/mail-archive/web/hybi/current/msg03228.html


I haven't seen any people in favor of your proposal, if you want still 
push for it then I suggest you
to write down a design of how your solution would work, with a full and 
complete technical description of the handshake:
describing what kind of NAT/Firewall you have in mind, how they are 
supposed to interact etc. etc.
(as Adam has provided for TLS/NPN)
so that people can eventually read your technical proposal and comment 
on the solution you are proposing.
You can send the solution in a mail or write down in a draft and submit 
it to the IETF and then advertise it
in this mailing list and then patiently wait for people to comment it if 
they are interested.


Note also that this is not the right place to discuss the Security 
issues academically;
this wg is to discuss and solve Security issues that can be generate 
from technical solutions within the current version of the 
WebSocketProtocol draft
or from alternative design solutions proposed.


regards
/Sal


-- 
Salvatore Loreto
www.sloreto.com