Re: [AVT] Working Group Last Call: draft-ietf-avt-rtp-midi-format-13 and draft-ietf-avt-rtp-midi-guidelines-13

[lazzaro <lazzaro at eecs.berkeley.edu>]

Hi everyone,

On Dec 6, 2005, at 7:15 AM, Magnus Westerlund  
<magnus.westerlund at ericsson.com> wrote:
> The WG last calls have concluded.
>
> Some comments has been raised so an updated draft will be  
> submitted. As these changes are mostly editorial and effect only  
> the guidelines which are informational. Thus no second WG last call  
> will be held and instead as soon the updated drafts are available  
> it will be requested to be submitted.


I have submitted draft-ietf-avt-rtp-midi-guidelines-14.txt
and draft-ietf-avt-rtp-midi-format-14.txt to internet-drafts.
Also available via the Berkeley mirror site:

http://www.cs.berkeley.edu/~lazzaro/sa/pubs/txt/current-rtp-midi.txt
http://www.cs.berkeley.edu/~lazzaro/sa/pubs/txt/current-guide.txt

There was one normative change to the format document.
I discovered a typo in Appendix C.2.3, in the definition of
chapter inclusion parameters for Chapter C.  Per Magnus's
request, I post diffs for this section.

This C.2.3 paragraph below has changed in -14.txt:

[old version]

For Chapter C, the field list may take on values in the range 0 to 511.
A field value X in the range 0-255 refers to a controller number X, and
indicates that the controller number does not use enhanced Chapter C
encoding.  A field value X in the range 256-511 refers to a controller
number "X minus 256", and indicates the controller number does use the
enhanced Chapter C encoding.

[new version]

For Chapter C, the field list may take on values in the range 0 to 255.
A field value X in the range 0-127 refers to a controller number X, and
indicates that the controller number does not use enhanced Chapter C
encoding.  A field value X in the range 128-255 refers to a controller
number "X minus 128", and indicates the controller number does use the
enhanced Chapter C encoding.

[end of diff]

---

In addition, the C.2.3 paragraph below has also changed:

[old version]

A Chapter C field list MUST NOT encode conflicting information about the
enhanced encoding status of a particular controller number.  For
example, values 0 and 256 MUST NOT both be coded by a field list.

[new version]

A Chapter C field list MUST NOT encode conflicting information about the
enhanced encoding status of a particular controller number.  For
example, values 0 and 128 MUST NOT both be coded by a field list.

[end of diff]

---
John Lazzaro
http://www.cs.berkeley.edu/~lazzaro
lazzaro [at] cs [dot] berkeley [dot] edu
---



_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
https://www1.ietf.org/mailman/listinfo/avt