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

Roni Even <ron.even.tlv@gmail.com> Thu, 01 June 2017 06:53 UTC

Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: avtext@ietf.org
Delivered-To: avtext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B3C34126D46; Wed, 31 May 2017 23:53:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <ron.even.tlv@gmail.com>
To: gen-art@ietf.org
Cc: avtext@ietf.org, draft-ietf-avtext-lrr.all@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149629998360.19813.14889515687249184753@ietfa.amsl.com>
Date: Wed, 31 May 2017 23:53:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/avtext/jNDOcy1R5sN6sUiHCoQ3WyPy29U>
Subject: [avtext] Genart last call review of draft-ietf-avtext-lrr-05
X-BeenThere: avtext@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 01 Jun 2017 06:53:04 -0000

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.
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. 
3.  What would an FCI with both TTID and TLID equal 0 mean.

Nits/editorial comments: 

1. Section 3 "an Real-Time Transport Control Protocol" should be "a
Real...".
2. In section 3 " [RFC5104](Section 3.5.1)" there is a link to section
3.5.1 but it does not work.
3. In section 3.2 "(see section Section 2.1)" section appears twice.