Internet DRAFT - draft-wang-tcpm-media-control-layer

draft-wang-tcpm-media-control-layer



Informational                                                     F.Wang
Internet Draft                           Beijing Institute of Technology
Intended status: Informational                                     Z.Fei
Expires: Nov 18, 2015                    Beijing Institute of Technology
                                                            May 18, 2015

       New Media Control Protocol Above TCP in Transmission Layer 
             draft-wang-tcpm-media-control-layer-02.txt

Abstract

   This document describes a new Media Control Protocol (MCP) above the 
   TCP layer in multimedia transimission network. The MCP have the label
   to show the classification of the data from the appliation layer.It 
   also can identify and label the transimission in wired or wireless 
   mode. These tags can optimize the TCP transimission with different 
   methods. 

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on May 18, 2015.

Copyright and License Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document. Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

F.Wang                    Expires Nov 18, 2015                  [Page 1]

New Media Control Protocol Above TCP in Transmission Layer  May 18, 2015

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Conventions used in this document  . . . . . . . . . . . . . .  3
   3.  Media Control Protocol . . . . . . . . . . . . . . . . . . . .  3
     3.1.  The framework of the MCP . . . . . . . . . . . . . . . . .  3
     3.2.  The tags in the MCP header . . . . . . . . . . . . . . . .  3
     3.3.  The work shceme of MCP . . . . . . . . . . . . . . . . . .  5
   4. The Extension of the MCP. . . . . . . . . . . . . . . . . . . .  5
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  5
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  5
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     7.1.  Normative References . . . . . . . . . . . . . . . . . . .  5
     7.2.  Informative References . . . . . . . . . . . . . . . . . .  5
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  5

1.  Introduction

   The TCP/IP is the most famous protocols. It provides the end-to-end
   connectivity in the network. The Transmission Control Protocol (TCP) 
   is one of the core protocols of the Internet protocol suite (IP), and 
   is so common that the entire suite is often called TCP/IP. TCP 
   provides reliable, ordered and error-checked delivery of a stream of 
   octets between programs running on computers connected to a local 
   area network, intranet or the public Internet. It resides at the 
   transport layer.But the TCP is designed for the data transmission 
   in the wired network. The packe loss in the wired network is about 
   10e-6, but in the mobile network is about 10e-3. And the download 
   throughtput has the giant decrease. Especially in the mobile wireless 
   network like LTE/WiMax, once the packet loss happened,the protocol 
   only take it as the congestion and decrease the receiving windows. 
   But in fact the packet loss is caused by the change of the wireless 
   environment.So TCP protocol only itself don't have the great 
   advantages in the wireless environment.

   In this document, a new Media Control Protocol (MCP) above the 
   TCP layer in multimedia transimission network. It combines with the 
   TCP in the transmission layers. The MCP have the label to show the 
   classification of the data from the appliation layer. It also can 
   identify and label the transimission in wired or wireless mode. These
   tags can optimize the TCP transimission with different methods. These
   methods include the TCP-Network Coding(TCP-NC), the new congestion 
   control method et. al.Especially in the wireless network, the MCP/TCP
   can provide the better QoE for the end users.

2.  Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

   In this document, these words will appear with that interpretation  
   only when in ALL CAPS. Lower case uses of these words are not to be 
   interpreted as carrying RFC-2119 significance.

F.Wang                    Expires Nov 18, 2015                  [Page 2]

New Media Control Protocol Above TCP in Transmission Layer  May 18, 2015

   A list of acronyms and abbreviations used in this document are
   presented below.

   o MCP: Media Control Protocol

   o TCP: Transmission Control Protocol

   o QoE: Quality of Experience

3.  Media Control Protocol

3.1.  The framework of the MCP 
   
   The MCP protocol is above the TCP protocol.It's not the new 
   indenpend layer,it must work with the TCP protocol. These two 
   protocol works in the transport layer.
   Just as show in Figure 2, it only adds the MCP header from the 
   application layer.This sturcture can guarantee the 
   
   +--------------------------------------------------------------+
   |                                         +---------+          |
   |	                                     |     Data|          |
   |                             +---------------------+          |
   |                             | TCP header|TCP data |          |
   |                     +-----------------------------+          |
   |                     |IP header|    IP       data  |          |
   |              +-------------------------------------------+   |
   |              |Header|     Frame               Data|Footer|   |
   |              +-------------------------------------------+   |
   +--------------------------------------------------------------+ 
    
             Figure 1. The framework of the TCP/IP suite
   
   +--------------------------------------------------------------+
   |                                              +----+          |
   |                                              |Data|          |
   |                        +--------------------------+          |
   |                        |          |MCP header|Data|          |
   |                        |TCP header|       TCP data|          |
   |              +------------------------------------+          |
   |              |IP header|    IP              data  |          |
   |       +--------------------------------------------------+   |
   |       |Header|     Frame                      Data|Footer|   |
   |       +--------------------------------------------------+   |
   +--------------------------------------------------------------+     
   
            Figure 2. The framework of the MCP/TCP/IP suite


3.2.  The tags in the MCP header
   
   
   
   
   
F.Wang                    Expires Nov 18, 2015                  [Page 3]

New Media Control Protocol Above TCP in Transmission Layer  May 18, 2015

   The MCP header is in 16 bits long. The detail is in Figure 3.

   +------------------------------------------------+
   |              MCP header                        |
   +------------------------------------------------+
   |Offsets Octet                                   |
   +------------------------------------------------+
   |      o        |     1               |          | 
   +------------------------------------------------+
   |0|1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|       |
   |VER|X|M| D | NET | OPT   |EXT        |       |
   +------------------------------------------------+
   |              MCP data                          |
   +------------------------------------------------+
             
	     Figure 3. The MCP header structure

   VER
   
   The ver is the version of the MCP. This is the first version.

   X
   
   The x is the extra with only 1 bit.If it is 1, it means the MCP has
   the extra header between the basic header and the data.

   M
   
   This is the tag to show the end of the data used by application.

   D
   
   This tag has 2 bits and can list 4 types of the data. In the first
   version, we only consider the text data or the media data.

   NET

   The net show the transmission environment in the wired network or the
   wireless network. This can help the TCP protocol optimize the 
   congestion avoidance algorithm. The 0x0 represents wireless network 
   and the 0x1 represents the cable network.

   OPT
   
   The optimization mechanism is the tags of different congestion
   method in TCP transmission.

   EXT 

   The extension is 4 bits for the future use.




  
F.Wang                    Expires Nov 18, 2015                  [Page 4]

New Media Control Protocol Above TCP in Transmission Layer  May 18, 2015

3.3.  The work shceme of MCP 
   
   TBD

4. The Extension of the MCP
   
   TBD

5.  Security Considerations

   Same security considerations of [RFC6247]

6.  IANA Considerations

   Same IANA considerations of [RFC6247].

7.  References

7.1.  Normative References

   [RFC6247] L. Eggert, "Moving the Undeployed TCP Extensions RFC 1072,
              RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC
              1644, and RFC 1693 to Historic Status", RFC 6247, May
              2011, <http://www.rfc-editor.org/info/rfc6247>.

   [RFC4022]  Raghunarayan, R., "Management Information Base for the
              Transmission Control Protocol (TCP)", RFC 4022, March
              2005

7.2.  Informative References


Authors' Addresses

   Fei Wang
   Beijing Institute of Technology
   5 South Zhongguancun Street, Haidian District, Beijing, China

   Email: fei_wang@bit.edu.cn
 

   Zesong Fei
   Beijing Institute of Technology
   5 South Zhongguancun Street, Haidian District, Beijing, China

   Email: feizesong@bit.edu.cn   









F.Wang                    Expires Nov 18, 2015                  [Page 5]