<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:0in;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
p.Preformatted, li.Preformatted, div.Preformatted
{mso-style-name:Preformatted;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
text-autospace:none;
font-size:10.0pt;
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="#ffffff" text="#000000">
I'm sure most of us know about this already. I suspect this means we
can regard it as relatively stable, so it might be worth including
in our considerations.<br>
<br>
Harald<br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject: </th>
<td>[AVTCORE] Request to publish
draft-ietf-avtcore-ecn-for-rtp-06</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
<td>Wed, 7 Mar 2012 11:28:33 +0200</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
<td>Roni Even <a class="moz-txt-link-rfc2396E" href="mailto:ron.even.tlv@gmail.com"><ron.even.tlv@gmail.com></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td><a class="moz-txt-link-rfc2396E" href="mailto:iesg-secretary@ietf.org"><iesg-secretary@ietf.org></a>, "'Robert Sparks'"
<a class="moz-txt-link-rfc2396E" href="mailto:rjsparks@nostrum.com"><rjsparks@nostrum.com></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">CC: </th>
<td>'Magnus Westerlund'
<a class="moz-txt-link-rfc2396E" href="mailto:magnus.westerlund@ericsson.com"><magnus.westerlund@ericsson.com></a>,
<a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-avtcore-ecn-for-rtp.all@tools.ietf.org">draft-ietf-avtcore-ecn-for-rtp.all@tools.ietf.org</a>,
<a class="moz-txt-link-abbreviated" href="mailto:avt@ietf.org">avt@ietf.org</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:0in;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
p.Preformatted, li.Preformatted, div.Preformatted
{mso-style-name:Preformatted;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
text-autospace:none;
font-size:10.0pt;
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi Robert,<o:p></o:p></p>
<p class="MsoNormal">I'd like to request that
draft-ietf-avtcore-ecn-for-rtp-06, Explicit Congestion
Notification (ECN) for RTP over UDP, be published as Standard
Track RFC. <o:p></o:p></p>
<p class="MsoNormal" style="">I've reviewed the draft in detail,
and the AVTCore working group was given the opportunity to
comment. The draft doesn't conflict with other work in AVTCore.
Accordingly, please consider it for publication.<o:p></o:p></p>
<p class="MsoNormal" style=""><o:p> </o:p></p>
<p class="MsoNormal" style="">Thanks,<o:p></o:p></p>
<p class="MsoNormal" style="">Roni Even<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height:
normal;"><span style="color: black;"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height:
normal;"><span style="color: black;"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">(1.a) Who is the
Document Shepherd for this document? Has the<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> Document
Shepherd personally reviewed this version of the <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> document
and, in particular, does he or she believe this <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> version
is ready for forwarding to the IESG for publication? <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="MsoNormal" style="">The document shepherd is Roni Even.
I have reviewed the document, and believe it is ready for
publication.<o:p></o:p></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> (1.b) Has the
document had adequate review both from key WG members <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> and from
key non-WG members? Does the Document Shepherd have <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> any
concerns about the depth or breadth of the reviews that <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> have been
performed? <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">The document is
the result of an effort done by key WG members. It went
through Working Group last call and people had enough time to
review it. The document shepherd feels comfortable with the
review it got.<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">Note that the
document started at AVT before it was moved to the new AVTCore
WG.<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> (1.c) Does the
Document Shepherd have concerns that the document <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> needs
more review from a particular or broader perspective, <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> e.g.,
security, operational complexity, someone familiar with <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> AAA,
internationalization or XML? <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">No concerns<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> (1.d) Does the
Document Shepherd have any specific concerns or <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> issues
with this document that the Responsible Area Director<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> and/or
the IESG should be aware of? For example, perhaps he <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> or she is
uncomfortable with certain parts of the document, or <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> has
concerns whether there really is a need for it. In any <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> event, if
the WG has discussed those issues and has indicated <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> that it
still wishes to advance the document, detail those <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> concerns
here. Has an IPR disclosure related to this document <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> been
filed? If so, please include a reference to the <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> disclosure
and summarize the WG discussion and conclusion on <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> this
issue. <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">No Concerns. No
IPR disclosure related to this document or the previous
individual draft and AVT version was filed.<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> (1.e) How solid
is the WG consensus behind this document? Does it <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> represent
the strong concurrence of a few individuals, with <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> others
being silent, or does the WG as a whole understand and <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> agree
with it? <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">The document has
strong consensus the members of the AVTCore WG.<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> (1.f) Has
anyone threatened an appeal or otherwise indicated extreme <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> discontent?
If so, please summarise the areas of conflict in <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> separate
email messages to the Responsible Area Director. (It <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> should be
in a separate email because this questionnaire is <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> entered
into the ID Tracker.)<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">No<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> (1.g) Has the
Document Shepherd personally verified that the <o:p></o:p></span></p>
<p class="Preformatted" style="margin-left: 47.95pt;"><span
style="font-size: 11pt; font-family:
"Calibri","sans-serif";">document
satisfies all ID nits?(See the <a moz-do-not-send="true"
href="/id-info/checklist.html">Checklist</a> and <a
moz-do-not-send="true"
href="http://tools.ietf.org/tools/idnits/">idnits</a>).Boilerplate
checks are not enough; this check needs to be thorough. Has
the document met all formal review criteria it needs to, such
as the MIB Doctor, media type and URI type reviews? <o:p></o:p></span></p>
<p class="Preformatted" style="margin-left: 47.95pt;"><span
style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height:
normal;"><span style="color: black;">There is one warning that
is relevant:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height:
normal;"><span style="color: black;"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">== There are 3
instances of lines with private range IPv4 addresses in<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> the document.
If these are generic example addresses, they should<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> be changed to
use any of the ranges defined in RFC 5735 (or<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> successor):
192.0.2.x, 198.51.100.x or 203.0.113.x.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">They are
intentional as we have an SDP example of an end-point that is
NATed with the address 10.0.1.4. Both the o= and the ICE
candidate list thus contains such an 10.0.1.4 address. Thus I
don't see an issue of using private address ranges in the
example.<o:p></o:p></span></p>
<p class="Preformatted" style="margin-left: 47.95pt;"><span
style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> (1.h) Has the
document split its references into normative and <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> informative?
Are there normative references to documents that <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> are not
ready for advancement or are otherwise in an unclear <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> state? If
such normative references exist, what is the <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> strategy
for their completion? Are there normative references <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> that are
downward references, as described in [RFC3967]? If <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> so, list
these downward references to support the Area <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> Director
in the Last Call procedure for them [RFC3967]. <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">References are
split. There are no normative references to documents which
are not in RFC state<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">(1.i) Has the
Document Shepherd verified that the document IANA <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> consideration
section exists and is consistent with the body <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> of the
document? If the document specifies protocol <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> extensions,
are reservations requested in appropriate IANA <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> registries?
Are the IANA registries clearly identified? If <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> the
document creates a new registry, does it define the <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> proposed
initial contents of the registry and an allocation <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> procedure
for future registrations? Does it suggest a <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> reasonable
name for the new registry? See [RFC5226]. If the <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> document
describes an Expert Review process has Shepherd <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> conferred
with the Responsible Area Director so that the IESG <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> can
appoint the needed Expert during the IESG Evaluation?<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">The IANA
consideration section exists and is inline with the body of
the document.<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> (1.j) Has the
Document Shepherd verified that sections of the <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> document
that are written in a formal language, such as XML <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> code, BNF
rules, MIB definitions, etc., validate correctly in <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> an
automated checker? <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">The document
shepherd verified that the SDP signaling examples in section
12 are correct.<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> (1.k) The IESG
approval announcement includes a Document <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> Announcement
Write-Up. Please provide such a Document <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> Announcement
Write-Up? Recent examples can be found in the<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> "Action"
announcements for approved documents. The approval <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> announcement
contains the following sections: <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">Technical Summary
<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> Relevant
content can frequently be found in the abstract <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> and/or
introduction of the document. If not, this may be <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> an
indication that there are deficiencies in the abstract <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> or
introduction. <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height:
normal;">“<span style="color: black;">This memo specifies how
Explicit Congestion Notification (ECN) can be<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height:
normal;"><span style="color: black;"> used with the Real-time
Transport Protocol (RTP) running over UDP,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height:
normal;"><span style="color: black;"> using RTP Control
Protocol (RTCP) as a feedback mechanism. It<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height:
normal;"><span style="color: black;"> defines a new RTCP
Extended Report (XR) block for periodic ECN<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height:
normal;"><span style="color: black;"> feedback, a new RTCP
transport feedback message for timely reporting<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height:
normal;"><span style="color: black;"> of congestion events,
and a Session Traversal Utilities for NAT<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height:
normal;"><span style="color: black;"> (STUN) extension used in
the optional initialization method using<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height:
normal;"><span style="color: black;"> Interactive Connectivity
Establishment (ICE). Signalling and<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height:
normal;"><span style="color: black;"> procedures for
negotiation of capabilities and initialization methods<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height:
normal;"><span style="color: black;"> are also defined.”<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">Working Group
Summary <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> Was there
anything in WG process that is worth noting? For <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> example,
was there controversy about particular points or <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> were
there decisions where the consensus was particularly <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> rough? <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">There were no
controversy about the proposed solution and there was
consensus on all discussion points<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"><o:p> </o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";">Document Quality
<o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> Are there
existing implementations of the protocol? Have a <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> significant
number of vendors indicated their plan to <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> implement
the specification? Are there any reviewers that <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> merit
special mention as having done a thorough review, <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> e.g., one
that resulted in important changes or a <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> conclusion
that the document had no substantive issues? If <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> there was
a MIB Doctor, Media Type or other expert review, <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> what was
its course (briefly)? In the case of a Media Type <o:p></o:p></span></p>
<p class="Preformatted"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif";"> review,
on what date was the request posted? <o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The document shepherd is not aware of current
implementations. There was interest in this work by other
standard bodies like 3GPP and ITU-T SG16 who need to reference
it.<o:p></o:p></p>
<p class="MsoNormal">The SDP attributes and ICE options defined in
the document were sent to review in MMUSIC on <span
style="color: black;">September 30, 2011</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>