the Use Cases for the Application of Multi-Service Tag
draft-zhang-icn-uscamulsertag-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-06
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
N Working Group                                                       
Internet Draft                                                Zhang Wei 
Document: draft-zhang-icn-uscamulsertag-00.txt                  He Jing 
Expires: September 11, 2019                               China SAPPRFT 
                                                             March 2019 
                                                                        
    
           the Use Cases for the Application of Multi-Service Tag 
                      draft-zhang-icn-uscamulsertag-00 
    
    
Status of this Memo 
    
   This Internet-Draft is submitted in full conformance with the 
   provisions of BCP 78 and BCP 79. 
    
   Internet-Drafts are working documents of the Internet Engineering 
   Task Force (IETF).  Note that other groups may also distribute 
   working documents as Internet-Drafts.  The list of current Internet- 
   Drafts is at https://datatracker.ietf.org/drafts/current/. 
    
   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." 
    
   This Internet-Draft will expire on Nov 11, 2019. 
    
    
    
Abstract 
    
   Based on the important concepts and research challenges described in 
   RFC 7927, we consider multi-service tagging technology to be an 
   effective name mechanism for audio and video content in ICN. Since 
   audio and video traffic is the primary traffic transmitted over the 
   Internet, it will greatly advance the current Internet architecture 
   to the ICN architecture, the name mechanism for creating audio and 
   video content. This article discusses typical cases of improvements 
   using name mechanisms, including content resource exchange between 
   different ISPs, resource caching of content naming information, and 
   data distribution for different transmission quality requirements in 
   low latency environments. 
    
    
Conventions used in this document 
    
   In examples, "C:" and "S:" indicate lines sent by the client and 
   server respectively. 
 
 
Zhang                  Expires - September 2019               [Page 1] 

                   draft-zhang-icn-uscamulsertag-00         March 2019 
 
 
   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 [i]. 
    
Copyright Notice 
 
   Copyright (c) 2019 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. 
    
Table of Contents 
    
   1. Introduction...................................................2 
   2. Terminology and Acronyms.......................................3 
   3. Use cases......................................................3 
      3.1 content resource sharing across ISP network................3 
      3.2 cache according to the content naming information..........4 
      3.3 Media transmission for different latency levels............4 
   Security Considerations...........................................5 
   IANA Considerations...............................................5 
   References........................................................5 
   Author's Addresses................................................5 
    
    
1. Introduction 
   Now the network traffic presents a rapid increase trend, the 
   popularization of network audio and video and the diversified viewing 
   model modes support watch audio and video in anytime and 
   anywhere,which also results in the increase of network traffic. The 
   network audio and video Apps must provide terrific Quality of 
   experience(QoE). These trends represent a developing direction of 
   future networks. Recognition and handling of the application traffic 
   is a key factor for network operation. Each network application uses 
   different protocol and is deployed by different ISP, which 
   incompletely depends on the network operaters. The method of the 
   recognition of traffic and applications uses the fuzzy heuristic 
   modes which are based on the port scope and key information of the 
   traffic and are similar with the DPI technology, but this series of 
   technologies have some limitations. The heuristic methods can't 
   effectively solve the problem of traffic recognition 
   because they can't keep up with the synchronization update of 
Show full document text