RFC 7273 on RTP Clock Source Signalling

rfc-editor@rfc-editor.org Tue, 01 July 2014 01:48 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2AC61A01D6; Mon, 30 Jun 2014 18:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.577
X-Spam-Level:
X-Spam-Status: No, score=-94.577 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FRT_STOCK1=3.988, FRT_STOCK2=3.988, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 OBjhZ7SfJ1UC; Mon, 30 Jun 2014 18:48:55 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 5FFC11A038B; Mon, 30 Jun 2014 18:48:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6725718047C; Mon, 30 Jun 2014 18:48:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7273 on RTP Clock Source Signalling
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140701014846.6725718047C@rfc-editor.org>
Date: Mon, 30 Jun 2014 18:48:46 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/90dOTCueZ6N1o7O-phTPB1oPvUo
Cc: drafts-update-ref@iana.org, avt@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jul 2014 01:48:57 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7273

        Title:      RTP Clock Source Signalling 
        Author:     A. Williams, K. Gross,
                    R. van Brandenburg, H. Stokking
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2014
        Mailbox:    aidan.williams@audinate.com, 
                    kevin.gross@avanw.com, 
                    ray.vanbrandenburg@tno.nl,
                    hans.stokking@tno.nl
        Pages:      30
        Characters: 63009
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avtcore-clksrc-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7273.txt

NTP format timestamps are used by several RTP protocols for
synchronisation and statistical measurements.  This memo specifies
Session Description Protocol (SDP) signalling that identifies
timestamp reference clock sources and SDP signalling that identifies
the media clock sources in a multimedia session.

This document is a product of the Audio/Video Transport Core Maintenance 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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

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