Telechat Review of draft-ietf-rmt-fcast-08

Request Review of draft-ietf-rmt-fcast
Requested rev. no specific revision (document currently at 08)
Type Telechat Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2013-01-22
Requested 2013-01-24
Authors Vincent Roca, Brian Adamson
Draft last updated 2013-05-03
Completed reviews Genart Last Call review of -07 by Roni Even (diff)
Genart Telechat review of -08 by Roni Even
Secdir Last Call review of -07 by Chris Lonvick (diff)
Assignment Reviewer Roni Even 
State Completed
Review review-ietf-rmt-fcast-08-genart-telechat-even-2013-05-03
Reviewed rev. 08
Review result Ready
Review completed: 2013-05-03


I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at <>.


Please resolve these comments along with any other Last Call comments you may receive.




Reviewer: Roni Even

Review Date:2013–1–15

IETF LC End Date: 2013-1–22

IESG Telechat date: 


Summary: This draft is almost ready for publication as Standard track RFC




Major issues:


Minor issues:




I had some problem when reading the document about what is mandatory to support. The distinction between what is  required to be  supported and used is mentioned in section 5. Also section 3.3 discusses what compliant implementation is, but section 5 provides the full information. I think that it will be better to move section 5 before or at the beginning of section 3 or as part of  3.3.  no need to have the information twice.



In section 3.3 “

The support of GZIP encoding, or any other solution, remains optional.” I think that support is mandatory. 



Nits/editorial comments:

In section 5.1 at the end of first table “in-bound” should be “in-band”

In section 6 in the paragraph after the bullet points “possibly possibly”

In section 7 “This specification requires IANA to create two new registries” I think there are three new registries.

In section 7.1 second paragraph “registry registry”