RTP Payload Format for MIDI
RFC 4695

Note: This ballot was opened for revision 15 and is now closed.

(Allison Mankin) (was Discuss, Yes) Yes

Comment (2006-02-03)
No email
send info
All comments were addressed by the -15 versions.

(Brian Carpenter) No Objection

(Margaret Cullen) No Objection

(Bill Fenner) No Objection

(Ted Hardie) No Objection

Comment (2006-01-18 for -)
No email
send info
rtp-midi-guidelines has the following text:

We now show example code that implements the actions the parties take
during the session.  The code is written in C, and uses the sockets API
and other POSIX systems calls.  We show code for the first party (the
second party takes a symmetric set of actions).

I think it would be valuable to include references here; I can assume which C  
is meant by the reference to posix, but it can't hurt to nail it down.

The information in 6.2 on the target network characteristics seems like it would 
be valuable earlier, and it might be useful to consider adding to the introductory material.

(Scott Hollenbeck) (was Discuss) No Objection

(Russ Housley) No Objection

Comment (2006-01-18 for -)
No email
send info
  Please delete the change log prior to publication.

(David Kessens) No Objection

(Jon Peterson) No Objection

(Mark Townsley) No Objection

(Bert Wijnen) No Objection

Comment (2006-01-19 for -)
No email
send info
Document: draft-ietf-avt-rtp-midi-format-14.txt

Page 33:  c=IN IP6 FF1E:03AD::7F2E:172A:1E24
Page 95:  c=IN IP6 FF1E:03AD::7F2E:172A:1E24
Page 109: c=IN IP6 FF1E:03AD::7F2E:172A:1E24
Page 113: c=IN IP6 FF1E:03AD::7F2E:172A:1E24
Page 116: c=IN IP6 FF1E:03AD::7F2E:172A:1E24
Page 121: c=IN IP6 FF1E:03AD::7F2E:172A:1E24

These do not look like IPv6 example addresses as required per RFC3849.
That is, they should be from the set: 2001:DB8::/32

(Alex Zinin) No Objection