Re: [avtext] Genart last call review of draft-ietf-avtext-lrr-05

Roni Even <roni.even@huawei.com> Wed, 07 June 2017 07:39 UTC

Return-Path: <roni.even@huawei.com>
X-Original-To: avtext@ietfa.amsl.com
Delivered-To: avtext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8840912EAF0; Wed, 7 Jun 2017 00:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 bvuX8M425-Ch; Wed, 7 Jun 2017 00:39:23 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9210912EAEC; Wed, 7 Jun 2017 00:39:22 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DIA89554; Wed, 07 Jun 2017 07:39:20 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 7 Jun 2017 08:38:21 +0100
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by nkgeml412-hub.china.huawei.com (10.98.56.73) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 7 Jun 2017 15:38:18 +0800
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.49]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0301.000; Wed, 7 Jun 2017 15:38:11 +0800
From: Roni Even <roni.even@huawei.com>
To: Roni Even <roni.even@huawei.com>, Jonathan Lennox <jonathan@vidyo.com>, Roni Even <ron.even.tlv@gmail.com>
CC: "avtext@ietf.org" <avtext@ietf.org>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-avtext-lrr.all@ietf.org" <draft-ietf-avtext-lrr.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Index: AQHS2qO4IAQ0EK1qvUeY+IF4GawhgaIYtpMAgAAtEkCAACiLwA==
Date: Wed, 07 Jun 2017 07:38:10 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD7CFF80@DGGEMM506-MBX.china.huawei.com>
References: <149629998360.19813.14889515687249184753@ietfa.amsl.com> <BAFC5C7C-466C-4756-9AF1-A803196E7D25@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.201.114.24]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.5937ADA8.0169, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.49, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: e2a6e4c8b8332e96d28b21904c02d2cb
Archived-At: <https://mailarchive.ietf.org/arch/msg/avtext/WD56DAmlurqRdVSG4Oy-BVuII-U>
Subject: Re: [avtext] Genart last call review of draft-ietf-avtext-lrr-05
X-BeenThere: avtext@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Audio/Video Transport Extensions working group discussion list <avtext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avtext>, <mailto:avtext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avtext/>
List-Post: <mailto:avtext@ietf.org>
List-Help: <mailto:avtext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jun 2017 07:39:26 -0000

Hi Jonathan,
Just another clarification for both TTID=0 and TLID=0 , I understand that there is one base layer, but does this case have any special meaning?
Roni

> -----Original Message-----
> From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of Roni Even
> Sent: יום ד 07 יוני 2017 08:16
> To: Jonathan Lennox; Roni Even
> Cc: avtext@ietf.org; General Area Review Team; draft-ietf-avtext-
> lrr.all@ietf.org; ietf@ietf.org
> Subject: Re: [Gen-art] Genart last call review of draft-ietf-avtext-lrr-05
> 
> Hi Jonathan,
> I did not see the text you added yet as a response to my first question So to
> better clarify my question . If the FCI has TTID=0 and TLID=2 . does it mean
> that it is a request to update both?
> This was also the reason for the question about both TTID=0 and TLID=0,
> which layer need update or is it both?
> Can you say that you want just to update temporal or spatial?
> 
> Roni
> 
> > -----Original Message-----
> > From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of Jonathan
> > Lennox
> > Sent: יום ד 07 יוני 2017 00:30
> > To: Roni Even
> > Cc: draft-ietf-avtext-lrr.all@ietf.org; General Area Review Team;
> > avtext@ietf.org; ietf@ietf.org
> > Subject: Re: [Gen-art] Genart last call review of
> > draft-ietf-avtext-lrr-05
> >
> > Hi, Roni — thanks for your review.  Responses inline.
> >
> > > On Jun 1, 2017, at 2:53 AM, Roni Even <ron.even.tlv@gmail.com> wrote:
> > >
> > > Reviewer: Roni Even
> > > Review result: Ready with Issues
> > >
> > > I am the assigned Gen-ART reviewer for this draft. The General Area
> > > Review Team (Gen-ART) reviews all IETF documents being processed by
> > > the IESG for the IETF Chair.  Please treat these comments just like
> > > any other last call comments.
> > >
> > > For more information, please see the FAQ at
> > >
> > > <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> > >
> > > Document: draft-ietf-avtext-lrr-??
> > > Reviewer: Roni Even
> > > Review Date: 2017-05-31
> > > IETF LC End Date: 2017-06-08
> > > IESG Telechat date: Not scheduled for a telechat
> > >
> > > Summary:
> > > The document is ready with issues for a standard track RFC Major
> > > issues:
> > >
> > > Minor issues:
> > >
> > > 1. Can you specify both TTID and TLID in the same FCI.
> >
> > Syntactically, they must both occur.
> >
> > If you mean can you request an upgrade in both at once, yes; I’ve
> > added text to clarify this.
> >
> > > 2. What is the meaning of value 0 for TTID and TLID - TID or LID =0
> > > in frame marking draft means base layer if there is scalability.
> > >     This relates to the previous question.
> >
> > I’m not sure I understand this question.
> >
> > I’ve added text that if C=1, at least one of <TTID, TLID> MUST be
> > greater than <CTID, CLID>, and both MUST be greater than or equal to
> > their counterpart, so the LRR is actually requesting a layer upgrade.
> > Is that what you were asking about?
> >
> > > 3.  What would an FCI with both TTID and TLID equal 0 mean.
> >
> > It means you want a refresh of the base temporal/spatial layer, only.
> >
> > > Nits/editorial comments:
> > >
> > > 1. Section 3 "an Real-Time Transport Control Protocol" should be "a
> > > Real…".
> >
> > Colin pointed out that it should say “an RTP Control Protocol” anyway.
> >
> > > 2. In section 3 " [RFC5104](Section 3.5.1)" there is a link to
> > > section
> > > 3.5.1 but it does not work.
> >
> > xml2rfc doesn’t have any way to link to sections of other documents,
> > so the “(Section 3.5.1)” part is just a comment.
> >
> > I think the internet-draft tooling may have thought I was trying to
> > link to a non-existent section 3.5.1 of this document, but that’s outside my
> control.
> >
> > > 3. In section 3.2 "(see section Section 2.1)" section appears twice.
> >
> > Fixed.
> > _______________________________________________
> > Gen-art mailing list
> > Gen-art@ietf.org
> > https://www.ietf.org/mailman/listinfo/gen-art
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art