[ppsp] RFC 7846 on Peer-to-Peer Streaming Tracker Protocol (PPSTP)
rfc-editor@rfc-editor.org Wed, 01 June 2016 00:41 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96C8012D923; Tue, 31 May 2016 17:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level:
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IEZ-oOqzOXoT; Tue, 31 May 2016 17:41:22 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28F3312D916; Tue, 31 May 2016 17:41:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 15407B81287; Tue, 31 May 2016 17:41:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160601004122.15407B81287@rfc-editor.org>
Date: Tue, 31 May 2016 17:41:22 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ppsp/Mjshz5OqnLQXfZlrFvunP2MUA7s>
Cc: drafts-update-ref@iana.org, ppsp@ietf.org, rfc-editor@rfc-editor.org
Subject: [ppsp] RFC 7846 on Peer-to-Peer Streaming Tracker Protocol (PPSTP)
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: discussing to draw up peer to peer streaming protocol <ppsp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppsp>, <mailto:ppsp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppsp/>
List-Post: <mailto:ppsp@ietf.org>
List-Help: <mailto:ppsp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppsp>, <mailto:ppsp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2016 00:41:25 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7846
Title: Peer-to-Peer Streaming Tracker Protocol (PPSTP)
Author: R. Cruz, M. Nunes,
J. Xia, R. Huang, Ed.,
J. Taveira, D. Lingli
Status: Standards Track
Stream: IETF
Date: May 2016
Mailbox: rui.cruz@ieee.org,
mario.nunes@inov.pt,
xiajinwei@huawei.com,
rachel.huang@huawei.com,
joao.silva@inov.pt,
denglingli@chinamobile.com
Pages: 55
Characters: 120911
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ppsp-base-tracker-protocol-12.txt
URL: https://www.rfc-editor.org/info/rfc7846
DOI: http://dx.doi.org/10.17487/RFC7846
This document specifies the base Peer-to-Peer Streaming
Tracker Protocol (PPSTP) version 1, an application-layer control
(signaling) protocol for the exchange of meta information between
trackers and peers. The specification outlines the architecture of
the protocol and its functionality; it also describes message flows,
message processing instructions, message formats, formal syntax, and
semantics. The PPSTP enables cooperating peers to
form content-streaming overlay networks to support near real-time
delivery of structured media content (audio, video, and associated timed
text and metadata), such as adaptive multi-rate, layered (scalable),
and multi-view (3D) videos in live, time-shifted, and on-demand
modes.
This document is a product of the Peer to Peer Streaming Protocol Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC