Re: [MMUSIC] I-D Action: draft-ietf-mmusic-proto-iana-registration-01.txt
Suhas Nandakumar <suhasietf@gmail.com> Sun, 06 September 2015 23:23 UTC
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94EB41B2D99 for <mmusic@ietfa.amsl.com>; Sun, 6 Sep 2015 16:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 EBIqxaQQcPVu for <mmusic@ietfa.amsl.com>; Sun, 6 Sep 2015 16:23:01 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C81F1ACDA6 for <mmusic@ietf.org>; Sun, 6 Sep 2015 16:23:01 -0700 (PDT)
Received: by vkbf67 with SMTP id f67so35027038vkb.0 for <mmusic@ietf.org>; Sun, 06 Sep 2015 16:23:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XwqANLd2Ya1D6Rc0cTBB1uvBzRPN8BFUAmKVNPqtnR4=; b=NCWCJUwkKOdpyEZh0N3dsmAQPbR31ycp4NwJD0ylvhCEJeXySOs4kiDJnaa1HrtuUv caeDdkNoAm5Hy+35HLWX2Mp0v1xPxj92b5/GuZNozvpmN6isJrEBby0nDLzcNgx0tQjx hERUMsUeiZTjxWuzZ0KqucoZG8Bae05ujz71t05Gv31ASCLgFofrMKpi8zYS8GM6dGHv 7TlbEfpVKy551gpoqrG/DVT2wZf+KEulRmJSiW0GarSDO7ribwM16KB3BlL0w6z93JBL KZP7bdNRFmESZCP39jrYKYLbegA1CTiwgJ6AYAGAPb8oPGH3B5g3AfSVTvC6QMNkyD+7 DoBw==
MIME-Version: 1.0
X-Received: by 10.52.110.200 with SMTP id ic8mr22544789vdb.76.1441581780718; Sun, 06 Sep 2015 16:23:00 -0700 (PDT)
Received: by 10.103.88.28 with HTTP; Sun, 6 Sep 2015 16:23:00 -0700 (PDT)
In-Reply-To: <55E98255.5070502@cisco.com>
References: <20150702182216.31878.43553.idtracker@ietfa.amsl.com> <CAMRcRGQKgbPbNQ3TUUSRqnn9osEcJbSQVeYK5uC5-d=zCbwrTg@mail.gmail.com> <55E98255.5070502@cisco.com>
Date: Sun, 06 Sep 2015 16:23:00 -0700
Message-ID: <CAMRcRGR_YCBmK6cn2FuCaUDndSRSurpPZ4Gc_oY+Y6wM6tOYYw@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Content-Type: multipart/alternative; boundary="bcaec548a2f5f45b94051f1c69d8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/-YDa_e0nvv_Cl366VzDX7te_LYw>
Cc: "avtcore-chairs@tools.ietf.org" <avtcore-chairs@tools.ietf.org>, mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-proto-iana-registration-01.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Sep 2015 23:23:04 -0000
Hello Flemming Thanks for the review. Please see inline Cheers Suhas On Fri, Sep 4, 2015 at 4:36 AM, Flemming Andreasen <fandreas@cisco.com> wrote: > Hi Suhas > > I took a look at the draft which generally looks good to me. A couple of > comments for consideration: > > - Section 3, last paragraph says "An 'm' line that specifies these new > proto identifiers MUST further qualify the application-layer protocol using > an fmt identifier." > I don't think this is accurate. We are doing RTP and hence what will go in > the fmt parameter simply follows the normal SDP/RTP procedures, i.e. they > define the media format in question. > [suhas] : agreed. So is the suggestion to get rid of that line altogether ? > > > - Section 4 > I suggest we make the statement normative, i.e. s/is used/MUST be used/ > > [suhas] - will update > > - Section 5 > a) The document requests registration of new RTP Profile names (as defined > in the document). I'd like to hear from the AVTCORE chairs on that. > > b) The document also requests registration of other RTP profile names from > RFC 5764 that have only been added to the RTP Profile Name registry. > - Again, I'd like to hear from the AVTCORE chairs on this > - There is no indication on the front page that the document updates RFC > 5764 (which technically, I believe it does if we add these registrations). > > [Suhas] Sure, I will wait for AVTCore chairs to respond before updating. > > Thanks > > -- Flemming > > > > > On 7/2/15 2:24 PM, Suhas Nandakumar wrote: > > Hello All > > This is an updated version with Jonathan's comments incorporated. > Please let me know your thoughts. > > Cheers > Suhas > > On Thu, Jul 2, 2015 at 11:22 AM, <internet-drafts@ietf.org> wrote: > >> >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> This draft is a work item of the Multiparty Multimedia Session Control >> Working Group of the IETF. >> >> Title : IANA registrations of SDP 'proto' attribute for >> transporting RTP Media over TCP under various RTP profiles. >> Author : Suhas Nandakumar >> Filename : draft-ietf-mmusic-proto-iana-registration-01.txt >> Pages : 7 >> Date : 2015-07-02 >> >> Abstract: >> RTP provides end-to-end network transport functions suitable for >> applications transmitting real-time data such as audio, video or >> simulation data, over multicast or unicast network services. The >> data transport is augmented by a control protocol (RTCP) to allow >> monitoring of the data delivery in a manner scalable to large >> multicast networks, and to provide minimal control and identification >> functionality. >> >> The RTP specification [RFC3550] establishes a registry of profile >> names for use by higher-level control protocols, such as the SDP, to >> refer to the transport methods. This specification describes the >> following new SDP transport protocol identifiers for transporting RTP >> Media over TCP: 'TCP/RTP/AVPF', 'TCP/RTP/SAVP', 'TCP/RTP/SAVPF', >> 'TCP/DTLS/RTP/SAVP', 'TCP/DTLS/RTP/SAVPF', 'TCP/TLS/RTP/AVP', >> 'TCP/TLS/RTP/AVPF'. >> >> >> The IETF datatracker status page for this draft is: >> >> https://datatracker.ietf.org/doc/draft-ietf-mmusic-proto-iana-registration/ >> >> There's also a htmlized version available at: >> https://tools.ietf.org/html/draft-ietf-mmusic-proto-iana-registration-01 >> >> A diff from the previous version is available at: >> >> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-proto-iana-registration-01 >> >> >> Please note that it may take a couple of minutes from the time of >> submission >> until the htmlized version and diff are available at tools.ietf.org. >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> _______________________________________________ >> mmusic mailing list >> mmusic@ietf.org >> https://www.ietf.org/mailman/listinfo/mmusic >> > > > > _______________________________________________ > mmusic mailing listmmusic@ietf.orghttps://www.ietf.org/mailman/listinfo/mmusic > > >
- [MMUSIC] I-D Action: draft-ietf-mmusic-proto-iana… internet-drafts
- Re: [MMUSIC] I-D Action: draft-ietf-mmusic-proto-… Suhas Nandakumar
- Re: [MMUSIC] I-D Action: draft-ietf-mmusic-proto-… Flemming Andreasen
- Re: [MMUSIC] I-D Action: draft-ietf-mmusic-proto-… Suhas Nandakumar
- Re: [MMUSIC] I-D Action: draft-ietf-mmusic-proto-… Flemming Andreasen
- Re: [MMUSIC] I-D Action: draft-ietf-mmusic-proto-… Suhas Nandakumar