[Udp35] port443 draft

Marc Blanchet <marc.blanchet@viagenie.ca> Sat, 19 July 2014 23:09 UTC

From: Marc Blanchet <marc.blanchet@viagenie.ca>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0D0F5C42-EAF3-4D5A-8945-E7E6870F9A08"
Message-Id: <005CE08B-CEB5-4FB8-9A1A-E786479D557B@viagenie.ca>
Date: Sat, 19 Jul 2014 19:09:33 -0400
To: udp35@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Archived-At: http://mailarchive.ietf.org/arch/msg/udp35/_0GOQQQiS-sfVMWb1Sh_8gJsJNQ
Subject: [Udp35] port443 draft
Precedence: list

Hello,
 during our conversation tonight, Brian referred to a "port443" draft and pointed to me, since I authored the draft. Currently expired, waiting to get more stuff in it before resurrecting it. Consider it preliminary (for example, many statements need to be wordsmith and more documented). 

If you are interested in reading:

http://tools.ietf.org/id/draft-blanchet-iab-internetoverport443-02.txt

Implications of Blocking Outgoing Ports Except Ports 80 and 443
             draft-blanchet-iab-internetoverport443-02.txt

Abstract

   Users are often connected to Internet with very few outgoing ports
   available, such as only port 80 and 443 over TCP.  This situation has
   many implications on designing, deploying and using IETF protocols,
   such as encaspulating protocols within HTTP, difficulty to do traffic
   engineering, quality of service, peer-to-peer, multi-channel
   protocols or deploying new transport protocols.  This document
   describes the situation and its implications.


Regards, Marc.

[Udp35] port443 draft Marc Blanchet