Re: [payload] I-D Action: draft-ietf-avt-rtp-isac-03.txt

[Colin Perkins <[e-mail]>]

On 16 Jan 2013, at 21:43, [e-mail] wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Audio/Video Transport Payloads Working Group of the IETF.
> 
> 	Title           : RTP Payload Format for the iSAC Codec
> 	Author(s)       : Tina le Grand
>                          Paul E. Jones
>                          Pascal Huart
>                          Turaj Zakizadeh Shabestary
>                          Harald Alvestrand
> 	Filename        : draft-ietf-avt-rtp-isac-03.txt
> 	Pages           : 15
> 	Date            : 2013-01-16
> 
> Abstract:
>   iSAC is a proprietary wideband speech and audio codec developed by
>   Global IP Solutions (now part of Google), suitable for use in Voice
>   over IP applications.  This document describes the payload format for
>   iSAC generated bit streams within a Real-Time Protocol (RTP) packet.
>   Also included here are the necessary details for the use of iSAC with
>   the Session Description Protocol (SDP).
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-avt-rtp-isac


One quick comment: the examples in Sections 6.1 and 6.2 use RFC 2119 language ("SHOULD"), but I don't think an example is the right place to define normative requirements for implementations. Can the RFC 2119 terms be removed from these sections (and possibly be replaced by references to a section where the response is defined)?

-- 
Colin Perkins
http://csperkins.org/