[prev in list] [next in list] [prev in thread] [next in thread]
List: ietf
Subject: RE: Request for Operations Directorate Review of
From: Bernard Aboba <bernard_aboba () hotmail ! com>
Date: 2011-02-27 1:45:40
Message-ID: BLU152-w632AA289B4BB351AE9FEDC93DF0 () phx ! gbl
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I reviewed the document draft-ietf-payload-rfc4695-bis in general
and for its operational impact.
Operations directorate reviews are solicited primarily to help the area
directors improve their efficiency, particularly when preparing for IESG
telechats, and allowing them to focus on documents requiring their attention
and spend less time on the trouble-free ones.
Improving the documents is important, but clearly a secondary purpose.
A third purpose is to broaden the OpsDir reviewers' exposure to work going
on in other parts of the IETF.
Reviews from OpsDir members do not in and of themselves cause the IESG to
raise issue with a document. The reviews may, however, convince individual
IESG members to raise concern over a particular document requiring further
discussion. The reviews, particularly those conducted in last call and
earlier, may also help the document editors improve their documents.
--
Review Summary:
Intended status: Standards Track
The document provides an updated specification for the RTP
payload format for MIDI, suitable for applications such as
musical performances. The primary reason for the update was
to address errors found in RFC 4695 by reviewers.
Is the document readable?
Yes.
Does it contain nits?
Possibly:
idnits 2.12.07:
tmp/draft-ietf-payload-rfc4695-bis-01.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
http://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
No issues found here.
Checking nits according to http://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
No issues found here.
Checking nits according to http://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
-- The draft header indicates that this document obsoletes RFC4695, but the
abstract doesn't seem to mention this, which it should.
Miscellaneous warnings:
----------------------------------------------------------------------------
-- The document date (February 8, 2011) is 19 days in the past. Is this
intentional?
Checking references for intended status: Proposed Standard
----------------------------------------------------------------------------
(See RFCs 3967 and 4897 for information about using normative references
to lower-maturity documents in RFCs)
== Unused Reference: 'RFC3986' is defined on line 7122, but no explicit
reference was found in the text
'[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform...'
-- Possible downref: Non-RFC (?) normative reference: ref. 'MIDI'
-- Possible downref: Non-RFC (?) normative reference: ref. 'MPEGSA'
-- Possible downref: Non-RFC (?) normative reference: ref. 'MPEGAUDIO'
-- Possible downref: Non-RFC (?) normative reference: ref. 'DLS2'
-- Possible downref: Non-RFC (?) normative reference: ref. 'RP015'
Summary: 0 errors (**), 1 warning (==), 7 comments (--).
--------------------------------------------------------------------------------
Is the document class appropriate?
Yes.
Is the problem well stated?
Yes.
Is the problem really a problem?
Yes.
Does the document consider existing solutions?
Yes. The document addresses issues found in RFC 4695. The differences are detailed \
in Appendix F, and there are no operational issues raised there (it's mostly ABNF \
corrections for SDP session management parameters).
Does the solution break existing technology?
No. This update is backward compatible with RFC 4695, other than the errors that \
were corrected.
Does the solution preclude future activity?
No.
Is the solution sufficiently configurable?
Yes. Negotiation is taken care of by SDP.
Can performance be measured? How?
Yes, using RTCP reporting.
Does the solution scale well?
Yes. The document defines both multicast and unicast transport.
Is Security Management discussed?
Security considerations are addressed in Section 9.
------------------------------------------------
Hello,
As a member of the Operations Directorate you are being asked to review
the following draft which is in IETF last call for it's operational
impact.
IETF Last Call:
The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-payload-rfc4695-bis/
IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-payload-rfc4695-bis/
Please provide comments and review to the Ops-dir mailing list
(ops-dir@ietf.org) before 2011-02-23, and include the authors of the
draft as well.
A Check-list of possible questions/topics to address in an OPS-DIR
review may be found in Appendix A of RFC 5706.
Only include the questions that apply to your review.
The status of Operations Directorate Review could be found
http://trac.tools.ietf.org/area/ops/trac/wiki/Directorates
or
http://merlot.tools.ietf.org/tools/art/opsdir/index.cgi/t=4904/welcome
You could update the wiki page when you finish the review.
Thank you,
Tina
http://tinatsou.weebly.com
> > -----Original Message-----
> > From: Tina Tsou [mailto:tena@huawei.com]
> > Sent: Sunday, February 20, 2011 7:16 AM
> > To: Bernard_Aboba@hotmail.com
> > Cc: Romascanu, Dan (Dan); rbonica@juniper.net
> > Subject: Request for Operations Directorate Review of
> > draft-ietf-payload-rfc4695-bis-01 by 2011-02-23
> >
> > Hello,
> > As a member of the Operations Directorate you are being asked
> > to review the following draft which is in IETF last call for
> > it's operational impact.
> >
> > IETF Last Call:
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-payload-rfc4695-bis/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-payload-rfc4695-bis/
> >
> >
> > Please provide comments and review to the Ops-dir mailing list
> > (ops-dir@ietf.org) before 2011-02-23, and include the authors
> > of the draft as well.
> >
> > A Check-list of possible questions/topics to address in an
> > OPS-DIR review may be found in Appendix A of RFC 5706.
> > Only include the questions that apply to your review.
> >
> > The status of Operations Directorate Review could be found
> > http://trac.tools.ietf.org/area/ops/trac/wiki/Directorates
> > or
> > http://merlot.tools.ietf.org/tools/art/opsdir/index.cgi/t=4904/welcome
> > You could update the wiki page when you finish the review.
> >
> >
> > Thank you,
> > Tina
> > http://tinatsou.weebly.com
> >
> >
> >
[Attachment #5 (text/html)]
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
I reviewed the document draft-ietf-payload-rfc4695-bis in general<br>and for its \
operational impact.<br> <br>Operations directorate reviews are solicited \
primarily to help the area<br>directors improve their efficiency, particularly when \
preparing for IESG<br>telechats, and allowing them to focus on documents requiring \
their attention<br>and spend less time on the trouble-free ones.<br><br>Improving the \
documents is important, but clearly a secondary purpose.<br>A third purpose is to \
broaden the OpsDir reviewers' exposure to work going<br>on in other parts of the \
IETF.<br> <br>Reviews from OpsDir members do not in and of themselves cause the \
IESG to<br>raise issue with a document. The reviews may, however, convince \
individual<br>IESG members to raise concern over a particular document requiring \
further<br>discussion. The reviews, particularly those conducted in last call \
and<br>earlier, may also help the document editors improve their \
documents.<br> <br>--<br> <br>Review Summary: <br>Intended status: \
Standards Track<br> <br> The document provides an updated \
specification for the RTP <br> payload format for MIDI, suitable for \
applications such as<br> musical performances. The primary reason \
for the update was<br> to address errors found in RFC 4695 by \
reviewers. <br><br>Is the document readable?<br><br>Yes. <br> <br>Does it \
contain nits?<br><br>Possibly:<br><br>idnits \
2.12.07:<br><br>tmp/draft-ietf-payload-rfc4695-bis-01.txt:<br><br> Checking \
boilerplate required by RFC 5378 and the IETF Trust (see<br> \
http://trustee.ietf.org/license-info):<br> \
----------------------------------------------------------------------------<br><br> \
No issues found here.<br><br> Checking nits according to \
http://www.ietf.org/id-info/1id-guidelines.txt:<br> \
----------------------------------------------------------------------------<br><br> \
No issues found here.<br><br> Checking nits according to \
http://www.ietf.org/id-info/checklist :<br> \
----------------------------------------------------------------------------<br><br> \
-- The draft header indicates that this document obsoletes RFC4695, but \
the<br> abstract doesn't seem to mention this, which it \
should.<br><br><br> Miscellaneous warnings:<br> \
----------------------------------------------------------------------------<br><br> \
-- The document date (February 8, 2011) is 19 days in the past. Is \
this<br> intentional?<br><br><br> Checking references \
for intended status: Proposed Standard<br> \
----------------------------------------------------------------------------<br><br> \
(See RFCs 3967 and 4897 for information about using normative \
references<br> to lower-maturity documents in \
RFCs)<br><br> == Unused Reference: 'RFC3986' is defined on line 7122, but no \
explicit<br> reference was found in the \
text<br> '[RFC3986] Berners-Lee, T., Fielding, \
R., and L. Masinter, "Uniform...'<br><br> -- Possible downref: Non-RFC (?) \
normative reference: ref. 'MIDI'<br><br> -- Possible downref: Non-RFC (?) \
normative reference: ref. 'MPEGSA'<br><br> -- Possible downref: Non-RFC (?) \
normative reference: ref. 'MPEGAUDIO'<br><br> -- Possible downref: Non-RFC (?) \
normative reference: ref. 'DLS2'<br><br> -- Possible downref: Non-RFC (?) \
normative reference: ref. 'RP015'<br><br><br> Summary: 0 \
errors (**), 1 warning (==), 7 comments \
(--).<br>--------------------------------------------------------------------------------<br> <br>Is \
the document class appropriate?<br><br>Yes.<br><br>Is the problem well \
stated?<br><br>Yes.<br><br>Is the problem really a problem?<br><br>Yes.<br><br>Does \
the document consider existing solutions?<br><br>Yes. The document addresses issues \
found in RFC 4695. The differences are detailed in Appendix F, and there \
are<br>no operational issues raised there (it's mostly ABNF corrections for SDP \
session management parameters).<br> <br>Does the solution break existing \
technology?<br><br>No. This update is backward compatible with RFC 4695, other \
than the errors that were corrected.<br> <br>Does the solution preclude future \
activity?<br> <br>No. <br> <br>Is the solution sufficiently \
configurable?<br><br>Yes. Negotiation is taken care of by SDP. \
<br> <br>Can performance be measured? How?<br> <br>Yes, using RTCP \
reporting. <br> <br>Does the solution scale well?<br><br>Yes. The document \
defines both multicast and unicast transport. <br> <br>Is Security \
Management discussed? <br><br>Security considerations are addressed in Section 9. \
<br> <br>------------------------------------------------<br>Hello,<br>As a \
member of the Operations Directorate you are being asked to review<br>the following \
draft which is in IETF last call for it's operational<br>impact.<br> <br>IETF \
Last Call:<br>The file can be obtained \
via<br>http://datatracker.ietf.org/doc/draft-ietf-payload-rfc4695-bis/<br> <br>IESG \
discussion can be tracked \
via<br>http://datatracker.ietf.org/doc/draft-ietf-payload-rfc4695-bis/<br> <br>Please \
provide comments and review to the Ops-dir mailing list<br>(ops-dir@ietf.org) before \
2011-02-23, and include the authors of the<br>draft as well.<br> <br>A \
Check-list of possible questions/topics to address in an OPS-DIR <br>review may be \
found in Appendix A of RFC 5706.<br>Only include the questions that apply to your \
review.<br> <br>The status of Operations Directorate Review could be \
found<br>http://trac.tools.ietf.org/area/ops/trac/wiki/Directorates<br>or<br>http://merlot.tools.ietf.org/tools/art/opsdir/index.cgi/t=4904/welcome<br>You \
could update the wiki page when you finish the review.<br> <br> <br>Thank \
you,<br>Tina<br>http://tinatsou.weebly.com<br><br><br><br>> > -----Original \
Message-----<br>> > From: Tina Tsou [mailto:tena@huawei.com] <br>> > \
Sent: Sunday, February 20, 2011 7:16 AM<br>> > To: \
Bernard_Aboba@hotmail.com<br>> > Cc: Romascanu, Dan (Dan); \
rbonica@juniper.net<br>> > Subject: Request for Operations Directorate Review \
of <br>> > draft-ietf-payload-rfc4695-bis-01 by 2011-02-23<br>> > \
<br>> > Hello,<br>> > As a member of the Operations Directorate you are \
being asked <br>> > to review the following draft which is in IETF last call \
for <br>> > it's operational impact.<br>> > <br>> > IETF Last \
Call:<br>> > The file can be obtained via<br>> > \
http://datatracker.ietf.org/doc/draft-ietf-payload-rfc4695-bis/<br>> > <br>> \
> IESG discussion can be tracked via<br>> > \
http://datatracker.ietf.org/doc/draft-ietf-payload-rfc4695-bis/<br>> > <br>> \
> <br>> > Please provide comments and review to the Ops-dir mailing \
list<br>> > (ops-dir@ietf.org) before 2011-02-23, and include the authors \
<br>> > of the draft as well.<br>> > <br>> > A Check-list of \
possible questions/topics to address in an <br>> > OPS-DIR review may be found \
in Appendix A of RFC 5706.<br>> > Only include the questions that apply to your \
review.<br>> > <br>> > The status of Operations Directorate Review could \
be found <br>> > \
http://trac.tools.ietf.org/area/ops/trac/wiki/Directorates<br>> > or<br>> \
> http://merlot.tools.ietf.org/tools/art/opsdir/index.cgi/t=4904/welcome<br>> \
> You could update the wiki page when you finish the review.<br>> > <br>> \
> <br>> > Thank you,<br>> > Tina<br>> > \
http://tinatsou.weebly.com<br>> > <br>> > <br>> > <br> \
</body> </html>
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic