
From nobody Sun Jan  4 12:47:29 2015
Return-Path: <juliusfriedman@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43D2F1A0040; Sun,  4 Jan 2015 12:47:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.703
X-Spam-Level: 
X-Spam-Status: No, score=0.703 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mbiXepx3DsWI; Sun,  4 Jan 2015 12:47:17 -0800 (PST)
Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD33E1A000F; Sun,  4 Jan 2015 12:47:16 -0800 (PST)
Received: by mail-pa0-f49.google.com with SMTP id eu11so27220026pac.36; Sun, 04 Jan 2015 12:47:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=2a6W1OsV9bdKh7zmCbZKG6xmt3CIcxSirL/bmMoxkiQ=; b=yssWkL2bK3CUJ/nybqNPNtFDNrLMF5rfBy8vYf5iKwwhr2+9FEM/fOCvS4HzqJh/Q7 N7hMZmNCMXUtM7lRitEBr1nJlpyl7ge1GzngtAPn76j3PoFNeJhicVuMTRp2KXSL56jA iGimCHrw+3q9piGNSVOv6TSQrrFKJxMwv4OiuFg8K+bekpj8GJnojTF3cFD/fMRUtW9A 44h7Mm3rFw2Rz4r/++DZnldhB0JDgfRLPWxNKRQPeHsw7uOHgNSbnUwNVqDeR3rPCC3s d/rOThkLX+lS2qkprHil78LtcSadwlMwZdMzpFXU+nf7XpDLKCyNI2bYZQmOTvpHeOSF xjYg==
MIME-Version: 1.0
X-Received: by 10.68.211.193 with SMTP id ne1mr142014273pbc.49.1420404435779;  Sun, 04 Jan 2015 12:47:15 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Sun, 4 Jan 2015 12:47:15 -0800 (PST)
In-Reply-To: <CACFvNHW9fr2ykT7tsGwCg8+k-JuxRPQVaLVK2sVdsdb_MFFeZw@mail.gmail.com>
References: <CACFvNHUz=VfYj+nz_WXbEvmzGvmNUiocCM1doPoPNJH+Qsemow@mail.gmail.com> <87a924c1xl.fsf@hobgoblin.ariadne.com> <CACFvNHXo4Jdmb9tsP-Yyoy3PAhLYO4_ubN4BoC4mDpgFYv_boQ@mail.gmail.com> <CACFvNHW9fr2ykT7tsGwCg8+k-JuxRPQVaLVK2sVdsdb_MFFeZw@mail.gmail.com>
Date: Sun, 4 Jan 2015 15:47:15 -0500
Message-ID: <CACFvNHVyhvd5MJi3mYL-4A4jTu2UTjmFwtORDx_mnV_TjGvirw@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: mmusic@ietf.org, avt@ietf.org
Content-Type: multipart/alternative; boundary=e89a8fb208e8d506c0050bd9add5
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/bCKxMb4sO898QpUBT2ywtrEnOP0
Subject: Re: [AVTCORE] Possible Erratta in RFC2326 relating to 'source' parameter.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Jan 2015 20:47:26 -0000

--e89a8fb208e8d506c0050bd9add5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Please find my previous message without the attachment which seems to have
been the result of why it was not received.

--------------------

I have come across several entities which use the 'source' datum but it
usually contains their own [IP] Address, I am not sure why giving another
[IP] Address there would be useful since it would probably be routed anyway=
.

I just wanted to make sure I wasn't missing anything and you came up with a
perfect answer so, Thank you !

I would like to also point out that it also is a security concern because
it can allow a client to connect to another server and this just looks like
part of the RTSP negotiation;

I can then technically also use any Rtsp server to DOS another server by
having it attempt to connect to that server to setup something repeatedly.

Additionally the server @ 'source' has no way of knowing the client would
even be connecting to it and the client may not even be allowed to.

This is the text verbatim:

   source:
          If the source address for the stream is different than can be
          derived from the RTSP endpoint address (the server in playback
          or the client in recording), the source MAY be specified.

The SDP has been exchanged and would then contain the necessary
information about connection information, the source is the 'EndPoint'
[IP] Address / Port pair from which the 'Request' has been received,
taking any other such notion of this would not be beneficial in any
circumstance, including `proxying` because the proxy would handle
'EndPoint' negotiation and have it's own set of headers to support
such.

Based on these concerns can `source` be amended to indicate it's only
such and not defined for use in the 'RTP/AVP' profile?

It would also reduce some of the work in the latest draft which
indicate concerns about this parameter.

.Since we are on the subject of the 'Transport' header I have another
question 'ssrc' in the same parameter, I have written into the
'mmusic' group several times but for some reason they don't seem to be
responding.

Can a client send his 'ssrc' to the server?
 - (Obviously he can but) Is this already legal with the current spec?
 - If so how can the server distinguish it's own `ssrc` in the response?
(E.g. if the server doesn't want that client to use that `ssrc` for some
reason)

Why would this need to be done? in situations where a client is joining a
session where many participants may already be active (especially
multicast) it would be beneficial to avoid early 'ssrc' collisions with one
of those.

Yes the client can already do this by just waiting for the response to
assign it's own `ssrc` but the response does not indicate the 'ssrc' of ALL
participants only that of the media server, rtcp eventually sorts this out
with a Goodbye and then a new ssrc but none the less I assume that saving
that time and bandwidth and also having the option to assign both client
and server ssrc would also have other benefits.

Moving back to the part about the peculiar punctuation.. I believe these
peculiarities come from a notion that everything was text based.

The latest draft makes no changes at all to this besides defining more
syntax.

Since the binary framing was apparently an after thought (based on
information from the drafts which show interleaved data in a 'DATA' RTSP
response) I think this was remnant from that in some way or at least that's
the best I can possibly imagine.

Why the framing octet would also be listed as a 'safe' character is beyond
me, there were several other characters / octets which definitely could
have been used e.g. 0xC3 -> 0xFF.

The fact that the document makes so many statements about ease of parsing
and then literally and figuratively destroy this concept with bad decisions
such as the framing character as well as the interesting syntax for the
markup.

I will past some of those here :

1.4 <https://tools.ietf.org/html/rfc2326#section-1.4> Protocol Properties

   RTSP has the following properties:

....

   Easy to parse:
          RTSP can be parsed by standard HTTP or MIME parsers.



...



4 <https://tools.ietf.org/html/rfc2326#section-4> RTSP Message

   RTSP is a text-based protocol and uses the ISO 10646 character set in
   UTF-8 encoding (RFC 2279 <https://tools.ietf.org/html/rfc2279>
[21]). Lines are terminated by CRLF, but
   receivers should be prepared to also interpret CR and LF by
   themselves as line terminators.

     Text-based protocols make it easier to add optional parameters in a
     self-describing manner. Since the number of parameters and the
     frequency of commands is low, processing efficiency is not a
     concern. Text-based protocols, if done carefully, also allow easy
     implementation of research prototypes in scripting languages such
     as Tcl, Visual Basic and Perl.

     The 10646 character set avoids tricky character set switching, but
     is invisible to the application as long as US-ASCII is being used.
     This is also the encoding used for RTCP. ISO 8859-1 translates
     directly into Unicode with a high-order octet of zero. ISO 8859-1
     characters with the most-significant bit set are represented as
     1100001x 10xxxxxx. (See RFC 2279
<https://tools.ietf.org/html/rfc2279> [21])

   RTSP messages can be carried over any lower-layer transport protocol
   that is 8-bit clean.

   Requests contain methods, the object the method is operating upon and
   parameters to further describe the method. Methods are idempotent,
   unless otherwise noted. Methods are also designed to require little
   or no state maintenance at the media server.



This literally becomes a nightmare when you have to reconstruct TCP
sequences.

I have attached a small 3MB zipped Wireshark capture which shows one such
case of my dealing with this issue.

This is only exacerbated by the fact the document allows packets up to the
maximum holding size in this mode AND specifies that packets with an
unknown context must be skipped...

Skipped how? Skipped as in past their header, past their data? Can that
text even be there?

We are talking about TCP and in such a case the data from a previous
segment was already received by the receiver and contains only some of the
data how would they skip data they have yet to receive?

I will explain why this is a security issue, Since there is no sequence
information in the binary header it must be trusted to contain valid length
values. Without inspecting the latter octets one can make no such
assumption about the type of binary data contained therein, especially if
there is no context assigned.

This if I can get a single TCP packet into a stream I can very easily
inject a lot of 'receive' space thus exponentially increasing my chances of
getting another packet into the stream.

I think that there should at the very least be a correlation between
'Block-Size' and the frame size such that frame sizes MUST NOT ever be
larger than that value if not already.

Furthermore I think that something needs to be done to specify how to deal
with nuisances such as 'more / less bytes available than indicated in
frame' especially when we also have 'Rtsp' messages which can be
interleaved at the same time in between frames (which can contain "$").

So to re-iterate my understanding of how things are in toto I have an
example I will outline below which is is a Rtsp Binary Interleaved sender
who tells a Rtsp Binary Interleaved client there is a frame of 48344 bytes
on channel 0.

The client received only 1328 bytes.

47016 bytes remain.

The client starts to receive again.

At this point there should only be the rest of the data in the frame (47016
bytes)

This data will come over several MSS sized segments, during which time the
socket may also be written to again (before the segment is transmitted to
the client).

{
    If the latter data happens to get to the receiver before the other
portions of the segment we have TCP 're-ordering' based on the sequence
number and may multiple ACK's for the early packets.

    If any data is missed we will have a re-transmission.

    The data being 'received' on the socket by the receiver coming from the
server comes from the data portion of the tcp packet which now contains
data from a previous segment.
}

The sender is now committed to sending the additional bytes as indicated
however if the sender stops sending this data or it's truncated it will
never make to the receiver. The stack will never be able to re-assemble the
packet and now framing sync is lost.

At this point ANY data consumed from the initial frame header and data
which was received must ALSO be dis-guarded but there is NO WAY for the
server to indicate this to the client... (This is why UDP is commonly used,
you get what you get and you don't what you don't)

There are a lot of articles outlining why TCP and RTP don't get along
mostly citing the overhead of re-transmissions so with Rtsp you think we
would have attempted to solve this not make it worse with bad encapsulation=
.

Something needs to be done about this because it's also a security concern,
e.g. if a client were to send a rtcp packet to the server which is very
larger and contains no data he could attempt to exhaust the resources of
that server (if they didn't monitor their rtcp bandwidth properly) or at
least force a higher amount of traffic.

So, information needs to be clear that there is no such thing as a packet
of less then 8 bytes under rtcp and 16 bytes under rtp. (Unless compression
is being used; ROHC or otherwise)

The null packet or any packet under 16 bytes would used for 'spacing' not a
'unknown' context, especially when I can have 255 channels, what unknown
context am I going to use then?

That is 4 octets for the `$` header, and the rest for the the packet header
which can then be inspected to be the same version, payloadtype and ssrc as
required by the client.

This prevents a client who may also send a "GET_PARAMETER" under
interleaved transport with weird headers and a body to attempt underflow
also which is something the current specification does nothing to protect
against.

"GET_PARAMATER rtsp://someuri/ RTSP/1.0\r\nCSeq:1\r\nDate:
xx:xx:xx\r\nContent-Length:24\r\n$UserAgent
$009\r\n$\0\0\aRTSP/1.$\0\0\r\n\r\nDatawith$IsNotAGoodIdea!\0\0"

This would allow applications to still take note of when a large frame was
seen but not be forced to act upon it and potentially lose data, and
depending on their implementation allow remote code execution.

I urge the committee to seriously look into these issues as they can have a
large impact.

https://isecpartners.github.io/fuzzing/vulnerabilities/2013/12/30/vlc-vulne=
rability.html

VLC seems protected against overflow after this but with some testing I
have determined that not only VLC but other servers and clients are
vulnerable to underflow this way as well making it both a server and client
issue.

I have more notes in my implementation @
https://net7mma.codeplex.com/SourceControl/latest#Rtp/RtpClient.cs if your
interested, it relates to one issue I saw where even though frame length
was good other data in the packet was invalid such as the 'Extension' or
the 'Length In Words Minus 1' or the ssrc etc.

Hopefully I didn't banter to much, it's rather late.

As for my other 'issues' / errata for RFC2435 has anything been determined
on them?

What about the one for RFC3550, has anyone sat down to do the math on that
one yet?

Thanks again for your time and response and have a Happy New Year if I
don't hear back by then!

Sincerely,
Julius Friedman


On Sun, Jan 4, 2015 at 3:28 PM, Julius Friedman <juliusfriedman@gmail.com>
wrote:

> This is a re-transmission of my previous response which didn't seem to
> make it to the list...
>
> Is there any way to confirm if I am properly signed up?
>
> I have come across several entities which use the 'source' datum but it
> usually contains their own [IP] Address, I am not sure why giving another
> [IP] Address there would be useful since it would probably be routed anyw=
ay.
>
> I just wanted to make sure I wasn't missing anything and you came up with
> a perfect answer so, Thank you !
>
> I would like to also point out that it also is a security concern because
> it can allow a client to connect to another server and this just looks li=
ke
> part of the RTSP negotiation;
>
> I can then technically also use any Rtsp server to DOS another server by
> having it attempt to connect to that server to setup something repeatedly=
.
>
> Additionally the server @ 'source' has no way of knowing the client would
> even be connecting to it and the client may not even be allowed to.
>
> This is the text verbatim:
>
>    source:
>           If the source address for the stream is different than can be
>           derived from the RTSP endpoint address (the server in playback
>           or the client in recording), the source MAY be specified.
>
> The SDP has been exchanged and would then contain the necessary informati=
on about connection information, the source is the 'EndPoint' [IP] Address =
/ Port pair from which the 'Request' has been received, taking any other su=
ch notion of this would not be beneficial in any circumstance, including `p=
roxying` because the proxy would handle 'EndPoint' negotiation and have it'=
s own set of headers to support such.
>
> Based on these concerns can `source` be amended to indicate it's only suc=
h and not defined for use in the 'RTP/AVP' profile?
>
> It would also reduce some of the work in the latest draft which indicate =
concerns about this parameter.
>
> .Since we are on the subject of the 'Transport' header I have another que=
stion 'ssrc' in the same parameter, I have written into the 'mmusic' group =
several times but for some reason they don't seem to be responding.
>
> Can a client send his 'ssrc' to the server?
>  - (Obviously he can but) Is this already legal with the current spec?
>  - If so how can the server distinguish it's own `ssrc` in the response?
> (E.g. if the server doesn't want that client to use that `ssrc` for some
> reason)
>
> Why would this need to be done? in situations where a client is joining a
> session where many participants may already be active (especially
> multicast) it would be beneficial to avoid early 'ssrc' collisions with o=
ne
> of those.
>
> Yes the client can already do this by just waiting for the response to
> assign it's own `ssrc` but the response does not indicate the 'ssrc' of A=
LL
> participants only that of the media server, rtcp eventually sorts this ou=
t
> with a Goodbye and then a new ssrc but none the less I assume that saving
> that time and bandwidth and also having the option to assign both client
> and server ssrc would also have other benefits.
>
> Moving back to the part about the peculiar punctuation.. I believe these
> peculiarities come from a notion that everything was text based.
>
> The latest draft makes no changes at all to this besides defining more
> syntax.
>
> Since the binary framing was apparently an after thought (based on
> information from the drafts which show interleaved data in a 'DATA' RTSP
> response) I think this was remnant from that in some way or at least that=
's
> the best I can possibly imagine.
>
> Why the framing octet would also be listed as a 'safe' character is beyon=
d
> me, there were several other characters / octets which definitely could
> have been used e.g. 0xC3 -> 0xFF.
>
> The fact that the document makes so many statements about ease of parsing
> and then literally and figuratively destroy this concept with bad decisio=
ns
> such as the framing character as well as the interesting syntax for the
> markup.
>
> I will past some of those here :
>
> 1.4 <https://tools.ietf.org/html/rfc2326#section-1.4> Protocol Properties
>
>    RTSP has the following properties:
>
> ....
>
>    Easy to parse:
>           RTSP can be parsed by standard HTTP or MIME parsers.
>
>
>
> ...
>
>
>
> 4 <https://tools.ietf.org/html/rfc2326#section-4> RTSP Message
>
>    RTSP is a text-based protocol and uses the ISO 10646 character set in
>    UTF-8 encoding (RFC 2279 <https://tools.ietf.org/html/rfc2279> [21]). =
Lines are terminated by CRLF, but
>    receivers should be prepared to also interpret CR and LF by
>    themselves as line terminators.
>
>      Text-based protocols make it easier to add optional parameters in a
>      self-describing manner. Since the number of parameters and the
>      frequency of commands is low, processing efficiency is not a
>      concern. Text-based protocols, if done carefully, also allow easy
>      implementation of research prototypes in scripting languages such
>      as Tcl, Visual Basic and Perl.
>
>      The 10646 character set avoids tricky character set switching, but
>      is invisible to the application as long as US-ASCII is being used.
>      This is also the encoding used for RTCP. ISO 8859-1 translates
>      directly into Unicode with a high-order octet of zero. ISO 8859-1
>      characters with the most-significant bit set are represented as
>      1100001x 10xxxxxx. (See RFC 2279 <https://tools.ietf.org/html/rfc227=
9> [21])
>
>    RTSP messages can be carried over any lower-layer transport protocol
>    that is 8-bit clean.
>
>    Requests contain methods, the object the method is operating upon and
>    parameters to further describe the method. Methods are idempotent,
>    unless otherwise noted. Methods are also designed to require little
>    or no state maintenance at the media server.
>
>
>
> This literally becomes a nightmare when you have to reconstruct TCP
> sequences.
>
> I have attached a small 3MB zipped Wireshark capture which shows one such
> case of my dealing with this issue.
>
> This is only exacerbated by the fact the document allows packets up to th=
e
> maximum holding size in this mode AND specifies that packets with an
> unknown context must be skipped...
>
> Skipped how? Skipped as in past their header, past their data? Can that
> text even be there?
>
> We are talking about TCP and in such a case the data from a previous
> segment was already received by the receiver and contains only some of th=
e
> data how would they skip data they have yet to receive?
>
> I will explain why this is a security issue, Since there is no sequence
> information in the binary header it must be trusted to contain valid leng=
th
> values. Without inspecting the latter octets one can make no such
> assumption about the type of binary data contained therein, especially if
> there is no context assigned.
>
> This if I can get a single TCP packet into a stream I can very easily
> inject a lot of 'receive' space thus exponentially increasing my chances =
of
> getting another packet into the stream.
>
> I think that there should at the very least be a correlation between
> 'Block-Size' and the frame size such that frame sizes MUST NOT ever be
> larger than that value if not already.
>
> Furthermore I think that something needs to be done to specify how to dea=
l
> with nuisances such as 'more / less bytes available than indicated in
> frame' especially when we also have 'Rtsp' messages which can be
> interleaved at the same time in between frames (which can contain "$").
>
> So to re-iterate my understanding of how things are in toto I have an
> example I will outline below which is is a Rtsp Binary Interleaved sender
> who tells a Rtsp Binary Interleaved client there is a frame of 48344 byte=
s
> on channel 0.
>
> The client received only 1328 bytes.
>
> 47016 bytes remain.
>
> The client starts to receive again.
>
> At this point there should only be the rest of the data in the frame
> (47016 bytes)
>
> This data will come over several MSS sized segments, during which time th=
e
> socket may also be written to again (before the segment is transmitted to
> the client).
>
> {
>     If the latter data happens to get to the receiver before the other
> portions of the segment we have TCP 're-ordering' based on the sequence
> number and may multiple ACK's for the early packets.
>
>     If any data is missed we will have a re-transmission.
>
>     The data being 'received' on the socket by the receiver coming from
> the server comes from the data portion of the tcp packet which now contai=
ns
> data from a previous segment.
> }
>
> The sender is now committed to sending the additional bytes as indicated
> however if the sender stops sending this data or it's truncated it will
> never make to the receiver. The stack will never be able to re-assemble t=
he
> packet and now framing sync is lost.
>
> At this point ANY data consumed from the initial frame header and data
> which was received must ALSO be dis-guarded but there is NO WAY for the
> server to indicate this to the client... (This is why UDP is commonly use=
d,
> you get what you get and you don't what you don't)
>
> There are a lot of articles outlining why TCP and RTP don't get along
> mostly citing the overhead of re-transmissions so with Rtsp you think we
> would have attempted to solve this not make it worse with bad encapsulati=
on.
>
> Something needs to be done about this because it's also a security
> concern, e.g. if a client were to send a rtcp packet to the server which =
is
> very larger and contains no data he could attempt to exhaust the resource=
s
> of that server (if they didn't monitor their rtcp bandwidth properly) or =
at
> least force a higher amount of traffic.
>
> So, information needs to be clear that there is no such thing as a packet
> of less then 8 bytes under rtcp and 16 bytes under rtp. (Unless compressi=
on
> is being used; ROHC or otherwise)
>
> The null packet or any packet under 16 bytes would used for 'spacing' not
> a 'unknown' context, especially when I can have 255 channels, what unknow=
n
> context am I going to use then?
>
> That is 4 octets for the `$` header, and the rest for the the packet
> header which can then be inspected to be the same version, payloadtype an=
d
> ssrc as required by the client.
>
> This prevents a client who may also send a "GET_PARAMETER" under
> interleaved transport with weird headers and a body to attempt underflow
> also which is something the current specification does nothing to protect
> against.
>
> "GET_PARAMATER rtsp://someuri/ RTSP/1.0\r\nCSeq:1\r\nDate:
> xx:xx:xx\r\nContent-Length:24\r\n$UserAgent
> $009\r\n$\0\0\aRTSP/1.$\0\0\r\n\r\nDatawith$IsNotAGoodIdea!\0\0"
>
> This would allow applications to still take note of when a large frame wa=
s
> seen but not be forced to act upon it and potentially lose data, and
> depending on their implementation allow remote code execution.
>
> I urge the committee to seriously look into these issues as they can have
> a large impact.
>
>
> https://isecpartners.github.io/fuzzing/vulnerabilities/2013/12/30/vlc-vul=
nerability.html
>
> VLC seems protected against overflow after this but with some testing I
> have determined that not only VLC but other servers and clients are
> vulnerable to underflow this way as well making it both a server and clie=
nt
> issue.
>
> I have more notes in my implementation @
> https://net7mma.codeplex.com/SourceControl/latest#Rtp/RtpClient.cs if
> your interested, it relates to one issue I saw where even though frame
> length was good other data in the packet was invalid such as the
> 'Extension' or the 'Length In Words Minus 1' or the ssrc etc.
>
> Hopefully I didn't banter to much, it's rather late.
>
> As for my other 'issues' / errata for RFC2435 has anything been determine=
d
> on them?
>
> What about the one for RFC3550, has anyone sat down to do the math on tha=
t
> one yet?
>
> Thanks again for your time and response and have a Happy New Year if I
> don't hear back by then!
>
> Sincerely,
> Julius Friedman
>
>
>
> On Tue, Dec 30, 2014 at 3:33 PM, Dale R. Worley <worley@ariadne.com>
> wrote:
>
>> Julius Friedman <juliusfriedman@gmail.com> writes:
>> >  Transport           =3D    "Transport" ":"
>> >                             1\#transport-spec
>>
>> In a few places, RFC 2326 seems to use "\#" in place of "#".  There
>> doesn't seem to be any documentation for this.  There seems to be other
>> peculiar punctuation as well, including "\$" and "$'$".
>>
>> > Since 'source' is not listed I don't know the syntax, I assumed it to
>> > be an "IPAddress" however the text sates "address" so I imagine if I
>> > found a 'source=3D1.2.3.4:1554' that would be valid however I want to
>> > make sure since there isn't any syntax specified in the RFC.
>>
>> It's not clear to me that there *is* a "source=3D" parameter for the
>> Transport header.  Yes, there is prose describing source as a datum, but
>> there's no BNF for a corresponding parameter, and a quick search doesn't
>> turn up any instance of "Transport:  ...source=3D..." in any RFC or I-D.
>>
>> However, "source=3D" is shown in
>> http://heim.ifi.uio.no/~meccano/reflector/smallclient.html
>>
>> > Also I would wonder is there any restriction on specifying a port or
>> > address range also ? e.g. 'source=3D1.2.3.4/321202/2'
>>
>> Well, I see "parameter =3D [...] ";" "destination" [ "=3D" address ]", a=
nd
>>
>>    address             =3D    host
>>
>>    host      =3D   <A legal Internet host domain name of IP address
>>                  (in dotted decimal form), as defined by Section 2.1
>>                  of RFC 1123 \cite{rfc1123}>
>>
>> so it looks like <address> cannot specifiy an address range or a port.
>> I'd expect the port to be specified by the "client_port" and
>> "server_port" parameters.
>>
>> (BTW, it looks to me like the first "of" in the definition of <host>
>> should be "or".)
>>
>> > I believe there was a similar issue with Rtp-Info headers which was
>> > fixed in 'biz' however this among other issues were not addressed and
>> > I am wondering if any other updates will be made to this RFC before
>> > 2.0 Draft is finalized.
>>
>> An RFC is never "updated", although it can be obsoleted by a later RFC
>> that entirely replaces it.
>>
>> Dale
>>
>
>
>

--e89a8fb208e8d506c0050bd9add5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style=3D"color:rgb(80,0,80);font-size:12.800000190734=
9px">Please find my previous message without the attachment which seems to =
have been the result of why it was not received.</div><div style=3D"color:r=
gb(80,0,80);font-size:12.8000001907349px"><br></div><div style=3D"color:rgb=
(80,0,80);font-size:12.8000001907349px">--------------------</div><div styl=
e=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><br></div><div style=
=3D"color:rgb(80,0,80);font-size:12.8000001907349px">I have come across sev=
eral entities which use the &#39;source&#39; datum but it usually contains =
their own [IP] Address, I am not sure why giving another [IP] Address there=
 would be useful since it would probably be routed anyway.</div><div style=
=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><br></div><div style=
=3D"color:rgb(80,0,80);font-size:12.8000001907349px">I just wanted to make =
sure I wasn&#39;t missing anything and you came up with a perfect answer so=
, Thank you !</div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907=
349px"><br></div><div style=3D"color:rgb(80,0,80);font-size:12.800000190734=
9px">I would like to also point out that it also is a security concern beca=
use it can allow a client to connect to another server and this just looks =
like part of the RTSP negotiation;=C2=A0</div><div style=3D"color:rgb(80,0,=
80);font-size:12.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80=
);font-size:12.8000001907349px">I can then technically also use any Rtsp se=
rver to DOS another server by having it attempt to connect to that server t=
o setup something repeatedly.=C2=A0</div><div style=3D"color:rgb(80,0,80);f=
ont-size:12.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80);fon=
t-size:12.8000001907349px">Additionally the server @ &#39;source&#39; has n=
o way of knowing the client would even be connecting to it and the client m=
ay not even be allowed to.</div><div style=3D"color:rgb(80,0,80);font-size:=
12.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80);font-size:12=
.8000001907349px">This is the text verbatim:</div><div style=3D"color:rgb(8=
0,0,80);font-size:12.8000001907349px"><br></div><div style=3D"color:rgb(80,=
0,80);font-size:12.8000001907349px"><pre style=3D"white-space:pre-wrap;colo=
r:rgb(0,0,0);word-wrap:break-word">   source:
          If the source address for the stream is different than can be
          derived from the RTSP endpoint address (the server in playback
          or the client in recording), the source MAY be specified.</pre><p=
re style=3D"white-space:pre-wrap;word-wrap:break-word"><font face=3D"arial,=
 sans-serif"><span style=3D"white-space:normal">The SDP has been exchanged =
and would then contain the necessary information about connection informati=
on, the source is the &#39;EndPoint&#39; [IP] Address / Port pair from whic=
h the &#39;Request&#39; has been received, taking any other such notion of =
this would not be beneficial in any circumstance, including `proxying` beca=
use the proxy would handle &#39;EndPoint&#39;=C2=A0negotiation and have it&=
#39;s own set of headers to support such.</span></font></pre><pre style=3D"=
white-space:pre-wrap;word-wrap:break-word"><pre style=3D"white-space:pre-wr=
ap;word-wrap:break-word"><font face=3D"arial, sans-serif"><span style=3D"wh=
ite-space:normal">Based on these concerns can `source` be=C2=A0amended=C2=
=A0to indicate it&#39;s only such and not defined for use in the &#39;RTP/A=
VP&#39; profile?</span></font></pre><pre style=3D"white-space:pre-wrap;word=
-wrap:break-word"><font face=3D"arial, sans-serif"><span style=3D"white-spa=
ce:normal">It would also reduce some of the work in the latest draft which =
indicate=C2=A0concerns=C2=A0about this parameter.</span></font></pre></pre>=
<pre style=3D"white-space:pre-wrap;word-wrap:break-word"><font face=3D"aria=
l, sans-serif"><span style=3D"white-space:normal">.Since we are on the subj=
ect of the &#39;Transport&#39; header I</span></font><span style=3D"font-fa=
mily:arial,sans-serif"> have another question &#39;ssrc&#39; in the same pa=
rameter, I have written into the &#39;mmusic&#39; group several times but f=
or some reason they don&#39;t seem to be responding.</span></pre></div><div=
 style=3D"color:rgb(80,0,80);font-size:12.8000001907349px">Can a client sen=
d his &#39;ssrc&#39; to the server?=C2=A0</div><div style=3D"color:rgb(80,0=
,80);font-size:12.8000001907349px">=C2=A0- (Obviously he can but) Is this a=
lready legal with the current spec?=C2=A0</div><div style=3D"color:rgb(80,0=
,80);font-size:12.8000001907349px">=C2=A0- If so how can the server disting=
uish it&#39;s own `ssrc` in the response? (E.g. if the server doesn&#39;t w=
ant that client to use that `ssrc` for some reason)</div><div style=3D"colo=
r:rgb(80,0,80);font-size:12.8000001907349px"><br></div><div style=3D"color:=
rgb(80,0,80);font-size:12.8000001907349px">Why would this need to be done? =
in situations where a client is joining a session where many participants m=
ay already be active (especially multicast) it would be beneficial to avoid=
 early &#39;ssrc&#39; collisions with one of those.</div><div style=3D"colo=
r:rgb(80,0,80);font-size:12.8000001907349px"><br></div><div style=3D"color:=
rgb(80,0,80);font-size:12.8000001907349px">Yes the client can already do th=
is by just waiting for the response to assign it&#39;s own `ssrc` but the r=
esponse does not indicate the &#39;ssrc&#39; of ALL participants only that =
of the media server, rtcp eventually sorts this out with a Goodbye and then=
 a new ssrc but none the less I assume that saving that time and bandwidth =
and also having the option to assign both client and server ssrc would also=
 have other benefits.</div><div style=3D"color:rgb(80,0,80);font-size:12.80=
00001907349px"><br></div><div style=3D"color:rgb(80,0,80);font-size:12.8000=
001907349px">Moving back to the part about the=C2=A0<span style=3D"font-siz=
e:12.8000001907349px">peculiar punctuation..=C2=A0</span>I believe these pe=
culiarities come from a notion that everything was text based.</div><div st=
yle=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><span style=3D"font=
-size:12.8000001907349px"><br></span></div><div style=3D"color:rgb(80,0,80)=
;font-size:12.8000001907349px"><span style=3D"font-size:12.8000001907349px"=
>The latest draft makes no changes at all to this besides defining more syn=
tax.</span></div><div style=3D"color:rgb(80,0,80);font-size:12.800000190734=
9px"><span style=3D"font-size:12.8000001907349px"><br></span></div><div sty=
le=3D"color:rgb(80,0,80);font-size:12.8000001907349px">Since the binary fra=
ming was apparently an after thought (based on information from the drafts =
which show interleaved data in a &#39;DATA&#39; RTSP response) I think this=
 was remnant from that in some way or at least that&#39;s the best I can po=
ssibly imagine.</div><div style=3D"color:rgb(80,0,80);font-size:12.80000019=
07349px"><br></div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907=
349px">Why the framing octet would also be listed as a &#39;safe&#39; chara=
cter is beyond me, there were several other characters / octets which defin=
itely could have been used e.g. 0xC3 -&gt; 0xFF.</div><div style=3D"color:r=
gb(80,0,80);font-size:12.8000001907349px"><br></div><div style=3D"color:rgb=
(80,0,80);font-size:12.8000001907349px">The fact that the document makes so=
 many statements about ease of parsing and then literally and figuratively =
destroy this concept with bad decisions such as the framing character as we=
ll as the interesting syntax for the markup.</div><div style=3D"color:rgb(8=
0,0,80);font-size:12.8000001907349px"><br></div><div style=3D"color:rgb(80,=
0,80);font-size:12.8000001907349px">I will past some of those here :</div><=
div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><br></div><di=
v style=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><pre style=3D"w=
hite-space:pre-wrap;font-size:1em;margin-top:0px;margin-bottom:0px;color:rg=
b(0,0,0)"><span style=3D"line-height:0pt;font-size:1em;font-weight:bold"><h=
3 style=3D"line-height:0pt;display:inline;font-size:1em"><a name=3D"14ab6a2=
d434927aa_14a9f8300a80f387_section-1.4" href=3D"https://tools.ietf.org/html=
/rfc2326#section-1.4" target=3D"_blank" style=3D"color:black;text-decoratio=
n:none">1.4</a> Protocol Properties</h3></span>

   RTSP has the following properties:

....

   Easy to parse:
          RTSP can be parsed by standard HTTP or MIME parsers.</pre><pre st=
yle=3D"white-space:pre-wrap;font-size:1em;margin-top:0px;margin-bottom:0px;=
color:rgb(0,0,0)"><br></pre><pre style=3D"white-space:pre-wrap;font-size:1e=
m;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre style=
=3D"white-space:pre-wrap;font-size:1em;margin-top:0px;margin-bottom:0px;col=
or:rgb(0,0,0)">...</pre><pre style=3D"white-space:pre-wrap;font-size:1em;ma=
rgin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre style=3D"wh=
ite-space:pre-wrap;font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb=
(0,0,0)"><br></pre><pre style=3D"white-space:pre-wrap;font-size:1em;margin-=
top:0px;margin-bottom:0px;color:rgb(0,0,0)"><pre style=3D"white-space:pre-w=
rap;font-size:1em;margin-top:0px;margin-bottom:0px"><span style=3D"line-hei=
ght:0pt;font-size:1em;font-weight:bold"><h2 style=3D"line-height:0pt;displa=
y:inline;font-size:1em"><a name=3D"14ab6a2d434927aa_14a9f8300a80f387_sectio=
n-4" href=3D"https://tools.ietf.org/html/rfc2326#section-4" target=3D"_blan=
k" style=3D"color:black;text-decoration:none">4</a> RTSP Message</h2></span=
>

   RTSP is a text-based protocol and uses the ISO 10646 character set in
   UTF-8 encoding (<a href=3D"https://tools.ietf.org/html/rfc2279" target=
=3D"_blank">RFC 2279</a> [21]). Lines are terminated by CRLF, but
   receivers should be prepared to also interpret CR and LF by
   themselves as line terminators.

     Text-based protocols make it easier to add optional parameters in a
     self-describing manner. Since the number of parameters and the
     frequency of commands is low, processing efficiency is not a
     concern. Text-based protocols, if done carefully, also allow easy
     implementation of research prototypes in scripting languages such
     as Tcl, Visual Basic and Perl.

     The 10646 character set avoids tricky character set switching, but
     is invisible to the application as long as US-ASCII is being used.
     This is also the encoding used for RTCP. ISO 8859-1 translates
     directly into Unicode with a high-order octet of zero. ISO 8859-1
     characters with the most-significant bit set are represented as
     1100001x 10xxxxxx. (See <a href=3D"https://tools.ietf.org/html/rfc2279=
" target=3D"_blank">RFC 2279</a> [21])

   RTSP messages can be carried over any lower-layer transport protocol
   that is 8-bit clean.

   Requests contain methods, the object the method is operating upon and
   parameters to further describe the method. Methods are idempotent,
   unless otherwise noted. Methods are also designed to require little
   or no state maintenance at the media server.</pre></pre></div><div style=
=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><br></div><div style=
=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><br></div><div style=
=3D"color:rgb(80,0,80);font-size:12.8000001907349px">This literally becomes=
 a nightmare when you have to reconstruct TCP sequences.<br></div><div styl=
e=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><br></div><div style=
=3D"color:rgb(80,0,80);font-size:12.8000001907349px">I have attached a smal=
l 3MB zipped Wireshark capture which shows one such case of my dealing with=
 this issue.</div><div style=3D"color:rgb(80,0,80);font-size:12.80000019073=
49px"><br></div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349=
px">This is only exacerbated by the fact the document allows packets up to =
the maximum holding size in this mode AND specifies that packets with an un=
known context must be skipped...</div><div style=3D"color:rgb(80,0,80);font=
-size:12.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80);font-s=
ize:12.8000001907349px">Skipped how? Skipped as in past their header, past =
their data? Can that text even be there?</div><div style=3D"color:rgb(80,0,=
80);font-size:12.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80=
);font-size:12.8000001907349px">We are talking about TCP and in such a case=
 the data from a previous segment was already received by the receiver and =
contains only some of the data how would they skip data they have yet to re=
ceive?=C2=A0</div><div style=3D"color:rgb(80,0,80);font-size:12.80000019073=
49px"><br></div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349=
px">I will explain why this is a security issue, Since there is no sequence=
 information in the binary header it must be trusted to contain valid lengt=
h values. Without inspecting the latter octets one can make no such assumpt=
ion about the type of binary data contained therein, especially if there is=
 no context assigned.</div><div style=3D"color:rgb(80,0,80);font-size:12.80=
00001907349px"><br></div><div style=3D"color:rgb(80,0,80);font-size:12.8000=
001907349px">This if I can get a single TCP packet into a stream I can very=
 easily inject a lot of &#39;receive&#39; space thus exponentially increasi=
ng my chances of getting another packet into the stream.</div><div style=3D=
"color:rgb(80,0,80);font-size:12.8000001907349px"><br></div><div style=3D"c=
olor:rgb(80,0,80);font-size:12.8000001907349px">I think that there should a=
t the very least be a correlation between &#39;Block-Size&#39; and the fram=
e size such that frame sizes MUST NOT ever be larger than that value if not=
 already.</div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349p=
x"><br></div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px"=
>Furthermore I think that something needs to be done to specify how to deal=
 with nuisances such as &#39;more / less bytes available than indicated in =
frame&#39; especially when we also have &#39;Rtsp&#39; messages which can b=
e interleaved at the same time in between frames (which can contain &quot;$=
&quot;).</div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px=
"><br></div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px">=
So to re-iterate my understanding of how things are in toto I have an examp=
le I will outline below which is is a Rtsp Binary Interleaved sender who te=
lls a Rtsp Binary Interleaved client there is a frame of 48344 bytes on cha=
nnel 0.</div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px"=
><br></div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px">T=
he client received only 1328 bytes.</div><div style=3D"color:rgb(80,0,80);f=
ont-size:12.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80);fon=
t-size:12.8000001907349px">47016 bytes remain.<br></div><div style=3D"color=
:rgb(80,0,80);font-size:12.8000001907349px"><br></div><div style=3D"color:r=
gb(80,0,80);font-size:12.8000001907349px">The client starts to receive agai=
n.</div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><br>=
</div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px">At thi=
s point there should only be the rest of the data in the frame (47016 bytes=
)</div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><br><=
/div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px">This da=
ta will come over several MSS sized segments, during which time the socket =
may also be written to again (before the segment is transmitted to the clie=
nt).</div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><b=
r></div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px">{</d=
iv><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px">=C2=A0 =
=C2=A0 If the latter data happens to get to the receiver before the other p=
ortions of the segment we have TCP &#39;re-ordering&#39; based on the seque=
nce number and may multiple ACK&#39;s for the early packets.</div><div styl=
e=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><br></div><div style=
=3D"color:rgb(80,0,80);font-size:12.8000001907349px">=C2=A0 =C2=A0 If any d=
ata is missed we will have a re-transmission.</div><div style=3D"color:rgb(=
80,0,80);font-size:12.8000001907349px"><br></div><div style=3D"color:rgb(80=
,0,80);font-size:12.8000001907349px">=C2=A0 =C2=A0 The data being &#39;rece=
ived&#39; on the socket by the receiver coming from the server comes from t=
he data portion of the tcp packet which now contains data from a previous s=
egment.<br></div><div style=3D"color:rgb(80,0,80);font-size:12.800000190734=
9px">}</div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px">=
<br></div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px">Th=
e sender is now committed to sending the additional bytes as indicated howe=
ver if the sender stops sending this data or it&#39;s truncated it will nev=
er make to the receiver. The stack will never be able to re-assemble the pa=
cket and now framing sync is lost.</div><div style=3D"color:rgb(80,0,80);fo=
nt-size:12.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80);font=
-size:12.8000001907349px">At this point ANY data consumed from the initial =
frame header and data which was received must ALSO be dis-guarded but there=
 is NO WAY for the server to indicate this to the client... (This is why UD=
P is commonly used, you get what you get and you don&#39;t what you don&#39=
;t)</div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><br=
></div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px">There=
 are a lot of articles outlining why TCP and RTP don&#39;t get along mostly=
 citing the overhead of re-transmissions so with Rtsp you think we would ha=
ve attempted to solve this not make it worse with bad encapsulation.</div><=
div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><br></div><di=
v style=3D"color:rgb(80,0,80);font-size:12.8000001907349px">Something needs=
 to be done about this because it&#39;s also a security concern, e.g. if a =
client were to send a rtcp packet to the server which is very larger and co=
ntains no data he could attempt to exhaust the resources of that server (if=
 they didn&#39;t monitor their rtcp bandwidth properly) or at least force a=
 higher amount of traffic.</div><div style=3D"color:rgb(80,0,80);font-size:=
12.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80);font-size:12=
.8000001907349px">So, information needs to be clear that there is no such t=
hing as a packet of less then 8 bytes under rtcp and 16 bytes under rtp. (U=
nless compression is being used; ROHC or otherwise)</div><div style=3D"colo=
r:rgb(80,0,80);font-size:12.8000001907349px"><br></div><div style=3D"color:=
rgb(80,0,80);font-size:12.8000001907349px">The null packet or any packet un=
der 16 bytes would used for &#39;spacing&#39; not a &#39;unknown&#39; conte=
xt, especially when I can have 255 channels, what unknown context am I goin=
g to use then?</div><div style=3D"color:rgb(80,0,80);font-size:12.800000190=
7349px"><br></div><div style=3D"color:rgb(80,0,80);font-size:12.80000019073=
49px">That is 4 octets for the `$` header, and the rest for the the packet =
header which can then be inspected to be the same version, payloadtype and =
ssrc as required by the client.</div><div style=3D"color:rgb(80,0,80);font-=
size:12.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80);font-si=
ze:12.8000001907349px">This prevents a client who may also send a &quot;GET=
_PARAMETER&quot; under interleaved transport with weird headers and a body =
to attempt underflow also which is something the current specification does=
 nothing to protect against.</div><div style=3D"color:rgb(80,0,80);font-siz=
e:12.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80);font-size:=
12.8000001907349px">&quot;GET_PARAMATER rtsp://someuri/ RTSP/1.0\r\nCSeq:1\=
r\nDate: xx:xx:xx\r\nContent-Length:24\r\n$UserAgent $009\r\n$\0\0\aRTSP/1.=
$\0\0\r\n\r\nDatawith$IsNotAGoodIdea!\0\0&quot;<br></div><div style=3D"colo=
r:rgb(80,0,80);font-size:12.8000001907349px"><br></div><div style=3D"color:=
rgb(80,0,80);font-size:12.8000001907349px">This would allow applications to=
 still take note of when a large frame was seen but not be forced to act up=
on it and potentially lose data, and depending on their implementation allo=
w remote code execution.</div><div style=3D"color:rgb(80,0,80);font-size:12=
.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80);font-size:12.8=
000001907349px">I urge the committee to seriously look into these issues as=
 they can have a large impact.</div><div style=3D"color:rgb(80,0,80);font-s=
ize:12.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80);font-siz=
e:12.8000001907349px"><a href=3D"https://isecpartners.github.io/fuzzing/vul=
nerabilities/2013/12/30/vlc-vulnerability.html" target=3D"_blank">https://i=
secpartners.github.io/fuzzing/vulnerabilities/2013/12/30/vlc-vulnerability.=
html</a></div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px=
"><br></div><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px">=
VLC seems protected against overflow after this but with some testing I hav=
e determined that not only VLC but other servers and clients are vulnerable=
 to underflow this way as well making it both a server and client issue.</d=
iv><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px"><br></div=
><div style=3D"color:rgb(80,0,80);font-size:12.8000001907349px">I have more=
 notes in my implementation @=C2=A0<a href=3D"https://net7mma.codeplex.com/=
SourceControl/latest#Rtp/RtpClient.cs" target=3D"_blank">https://net7mma.co=
deplex.com/SourceControl/latest#Rtp/RtpClient.cs</a>=C2=A0if your intereste=
d, it relates to one issue I saw where even though frame length was good ot=
her data in the packet was invalid such as the &#39;Extension&#39; or the &=
#39;Length In Words Minus 1&#39; or the ssrc etc.</div><div style=3D"color:=
rgb(80,0,80);font-size:12.8000001907349px"><br></div><div style=3D"color:rg=
b(80,0,80);font-size:12.8000001907349px">Hopefully I didn&#39;t banter to m=
uch, it&#39;s rather late.</div><div style=3D"color:rgb(80,0,80);font-size:=
12.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80);font-size:12=
.8000001907349px">As for my other &#39;issues&#39; / errata for RFC2435 has=
 anything been determined on them?</div><div style=3D"color:rgb(80,0,80);fo=
nt-size:12.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80);font=
-size:12.8000001907349px">What about the one for RFC3550, has anyone sat do=
wn to do the math on that one yet?</div><div style=3D"color:rgb(80,0,80);fo=
nt-size:12.8000001907349px"><br></div><div style=3D"color:rgb(80,0,80);font=
-size:12.8000001907349px">Thanks again for your time and response and have =
a Happy New Year if I don&#39;t hear back by then!</div><div style=3D"color=
:rgb(80,0,80);font-size:12.8000001907349px"><br></div><div style=3D"color:r=
gb(80,0,80);font-size:12.8000001907349px">Sincerely,</div><div style=3D"col=
or:rgb(80,0,80);font-size:12.8000001907349px">Julius Friedman</div><div><br=
></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On S=
un, Jan 4, 2015 at 3:28 PM, Julius Friedman <span dir=3D"ltr">&lt;<a href=
=3D"mailto:juliusfriedman@gmail.com" target=3D"_blank">juliusfriedman@gmail=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"lt=
r"><div class=3D"gmail_quote"><div dir=3D"ltr"><div>This is a re-transmissi=
on of my previous response which didn&#39;t seem to make it to the list...<=
/div><div><br></div><div>Is there any way to confirm if I am properly signe=
d up?</div><div><div class=3D"h5"><div><br></div><div>I have come across se=
veral entities which use the &#39;source&#39; datum but it usually contains=
 their own [IP] Address, I am not sure why giving another [IP] Address ther=
e would be useful since it would probably be routed anyway.</div><div><br><=
/div><div>I just wanted to make sure I wasn&#39;t missing anything and you =
came up with a perfect answer so, Thank you !</div><div><br></div><div>I wo=
uld like to also point out that it also is a security concern because it ca=
n allow a client to connect to another server and this just looks like part=
 of the RTSP negotiation;=C2=A0</div><div><br></div><div>I can then technic=
ally also use any Rtsp server to DOS another server by having it attempt to=
 connect to that server to setup something repeatedly.=C2=A0</div><div><br>=
</div><div>Additionally the server @ &#39;source&#39; has no way of knowing=
 the client would even be connecting to it and the client may not even be a=
llowed to.</div><div><br></div><div>This is the text verbatim:</div><div><b=
r></div><div><span><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;whit=
e-space:pre-wrap">   source:
          If the source address for the stream is different than can be
          derived from the RTSP endpoint address (the server in playback
          or the client in recording), the source MAY be specified.</pre></=
span><pre style=3D"word-wrap:break-word"><font face=3D"arial, sans-serif"><=
span style=3D"white-space:normal">The SDP has been exchanged and would then=
 contain the necessary information about connection information, the source=
 is the &#39;EndPoint&#39; [IP] Address / Port pair from which the &#39;Req=
uest&#39; has been received, taking any other such notion of this would not=
 be beneficial in any circumstance, including `proxying` because the proxy =
would handle &#39;EndPoint&#39;=C2=A0negotiation and have it&#39;s own set =
of headers to support such.</span></font></pre><pre style=3D"word-wrap:brea=
k-word"><pre style=3D"word-wrap:break-word"><font face=3D"arial, sans-serif=
"><span style=3D"white-space:normal">Based on these concerns can `source` b=
e=C2=A0amended=C2=A0to indicate it&#39;s only such and not defined for use =
in the &#39;RTP/AVP&#39; profile?</span></font></pre><pre style=3D"word-wra=
p:break-word"><font face=3D"arial, sans-serif"><span style=3D"white-space:n=
ormal">It would also reduce some of the work in the latest draft which indi=
cate=C2=A0concerns=C2=A0about this parameter.</span></font></pre></pre><pre=
 style=3D"word-wrap:break-word"><font face=3D"arial, sans-serif"><span styl=
e=3D"white-space:normal">.Since we are on the subject of the &#39;Transport=
&#39; header I</span></font><span style=3D"font-family:arial,sans-serif"> h=
ave another question &#39;ssrc&#39; in the same parameter, I have written i=
nto the &#39;mmusic&#39; group several times but for some reason they don&#=
39;t seem to be responding.</span></pre></div><div>Can a client send his &#=
39;ssrc&#39; to the server?=C2=A0</div><div>=C2=A0- (Obviously he can but) =
Is this already legal with the current spec?=C2=A0</div><div>=C2=A0- If so =
how can the server distinguish it&#39;s own `ssrc` in the response? (E.g. i=
f the server doesn&#39;t want that client to use that `ssrc` for some reaso=
n)</div><div><br></div><div>Why would this need to be done? in situations w=
here a client is joining a session where many participants may already be a=
ctive (especially multicast) it would be beneficial to avoid early &#39;ssr=
c&#39; collisions with one of those.</div><div><br></div><div>Yes the clien=
t can already do this by just waiting for the response to assign it&#39;s o=
wn `ssrc` but the response does not indicate the &#39;ssrc&#39; of ALL part=
icipants only that of the media server, rtcp eventually sorts this out with=
 a Goodbye and then a new ssrc but none the less I assume that saving that =
time and bandwidth and also having the option to assign both client and ser=
ver ssrc would also have other benefits.</div><div><br></div><div>Moving ba=
ck to the part about the=C2=A0<span style=3D"font-size:12.8000001907349px">=
peculiar punctuation..=C2=A0</span>I believe these peculiarities come from =
a notion that everything was text based.</div><div><span style=3D"font-size=
:12.8000001907349px"><br></span></div><div><span style=3D"font-size:12.8000=
001907349px">The latest draft makes no changes at all to this besides defin=
ing more syntax.</span></div><div><span style=3D"font-size:12.8000001907349=
px"><br></span></div><div>Since the binary framing was apparently an after =
thought (based on information from the drafts which show interleaved data i=
n a &#39;DATA&#39; RTSP response) I think this was remnant from that in som=
e way or at least that&#39;s the best I can possibly imagine.</div><div><br=
></div><div>Why the framing octet would also be listed as a &#39;safe&#39; =
character is beyond me, there were several other characters / octets which =
definitely could have been used e.g. 0xC3 -&gt; 0xFF.</div><div><br></div><=
div>The fact that the document makes so many statements about ease of parsi=
ng and then literally and figuratively destroy this concept with bad decisi=
ons such as the framing character as well as the interesting syntax for the=
 markup.</div><div><br></div><div>I will past some of those here :</div><di=
v><br></div><div><pre style=3D"font-size:1em;margin-top:0px;margin-bottom:0=
px;color:rgb(0,0,0)"><span style=3D"line-height:0pt;display:inline;font-siz=
e:1em;font-weight:bold"><h3 style=3D"line-height:0pt;display:inline;font-si=
ze:1em"><a name=3D"14ab6a2d434927aa_14a9f8300a80f387_section-1.4" href=3D"h=
ttps://tools.ietf.org/html/rfc2326#section-1.4" style=3D"color:black;text-d=
ecoration:none" target=3D"_blank">1.4</a> Protocol Properties</h3></span>

   RTSP has the following properties:

....

   Easy to parse:
          RTSP can be parsed by standard HTTP or MIME parsers.</pre><pre st=
yle=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br=
></pre><pre style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:r=
gb(0,0,0)"><br></pre><pre style=3D"font-size:1em;margin-top:0px;margin-bott=
om:0px;color:rgb(0,0,0)">...</pre><pre style=3D"font-size:1em;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre style=3D"font-size:1em=
;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre style=3D=
"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><pre styl=
e=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><span style=3D"line-he=
ight:0pt;display:inline;font-size:1em;font-weight:bold"><h2 style=3D"line-h=
eight:0pt;display:inline;font-size:1em"><a name=3D"14ab6a2d434927aa_14a9f83=
00a80f387_section-4" href=3D"https://tools.ietf.org/html/rfc2326#section-4"=
 style=3D"color:black;text-decoration:none" target=3D"_blank">4</a> RTSP Me=
ssage</h2></span>

   RTSP is a text-based protocol and uses the ISO 10646 character set in
   UTF-8 encoding (<a href=3D"https://tools.ietf.org/html/rfc2279" target=
=3D"_blank">RFC 2279</a> [21]). Lines are terminated by CRLF, but
   receivers should be prepared to also interpret CR and LF by
   themselves as line terminators.

     Text-based protocols make it easier to add optional parameters in a
     self-describing manner. Since the number of parameters and the
     frequency of commands is low, processing efficiency is not a
     concern. Text-based protocols, if done carefully, also allow easy
     implementation of research prototypes in scripting languages such
     as Tcl, Visual Basic and Perl.

     The 10646 character set avoids tricky character set switching, but
     is invisible to the application as long as US-ASCII is being used.
     This is also the encoding used for RTCP. ISO 8859-1 translates
     directly into Unicode with a high-order octet of zero. ISO 8859-1
     characters with the most-significant bit set are represented as
     1100001x 10xxxxxx. (See <a href=3D"https://tools.ietf.org/html/rfc2279=
" target=3D"_blank">RFC 2279</a> [21])

   RTSP messages can be carried over any lower-layer transport protocol
   that is 8-bit clean.

   Requests contain methods, the object the method is operating upon and
   parameters to further describe the method. Methods are idempotent,
   unless otherwise noted. Methods are also designed to require little
   or no state maintenance at the media server.</pre></pre></div><div><br><=
/div><div><br></div><div>This literally becomes a nightmare when you have t=
o reconstruct TCP sequences.<br></div><div><br></div><div>I have attached a=
 small 3MB zipped Wireshark capture which shows one such case of my dealing=
 with this issue.</div><div><br></div><div>This is only exacerbated by the =
fact the document allows packets up to the maximum holding size in this mod=
e AND specifies that packets with an unknown context must be skipped...</di=
v><div><br></div><div>Skipped how? Skipped as in past their header, past th=
eir data? Can that text even be there?</div><div><br></div><div>We are talk=
ing about TCP and in such a case the data from a previous segment was alrea=
dy received by the receiver and contains only some of the data how would th=
ey skip data they have yet to receive?=C2=A0</div><div><br></div><div>I wil=
l explain why this is a security issue, Since there is no sequence informat=
ion in the binary header it must be trusted to contain valid length values.=
 Without inspecting the latter octets one can make no such assumption about=
 the type of binary data contained therein, especially if there is no conte=
xt assigned.</div><div><br></div><div>This if I can get a single TCP packet=
 into a stream I can very easily inject a lot of &#39;receive&#39; space th=
us exponentially increasing my chances of getting another packet into the s=
tream.</div><div><br></div><div>I think that there should at the very least=
 be a correlation between &#39;Block-Size&#39; and the frame size such that=
 frame sizes MUST NOT ever be larger than that value if not already.</div><=
div><br></div><div>Furthermore I think that something needs to be done to s=
pecify how to deal with nuisances such as &#39;more / less bytes available =
than indicated in frame&#39; especially when we also have &#39;Rtsp&#39; me=
ssages which can be interleaved at the same time in between frames (which c=
an contain &quot;$&quot;).</div><div><br></div><div>So to re-iterate my und=
erstanding of how things are in toto I have an example I will outline below=
 which is is a Rtsp Binary Interleaved sender who tells a Rtsp Binary Inter=
leaved client there is a frame of 48344 bytes on channel 0.</div><div><br><=
/div><div>The client received only 1328 bytes.</div><div><br></div><div>470=
16 bytes remain.<br></div><div><br></div><div>The client starts to receive =
again.</div><div><br></div><div>At this point there should only be the rest=
 of the data in the frame (47016 bytes)</div><div><br></div><div>This data =
will come over several MSS sized segments, during which time the socket may=
 also be written to again (before the segment is transmitted to the client)=
.</div><div><br></div><div>{</div><div>=C2=A0 =C2=A0 If the latter data hap=
pens to get to the receiver before the other portions of the segment we hav=
e TCP &#39;re-ordering&#39; based on the sequence number and may multiple A=
CK&#39;s for the early packets.</div><div><br></div><div>=C2=A0 =C2=A0 If a=
ny data is missed we will have a re-transmission.</div><div><br></div><div>=
=C2=A0 =C2=A0 The data being &#39;received&#39; on the socket by the receiv=
er coming from the server comes from the data portion of the tcp packet whi=
ch now contains data from a previous segment.<br></div><div>}</div><div><br=
></div><div>The sender is now committed to sending the additional bytes as =
indicated however if the sender stops sending this data or it&#39;s truncat=
ed it will never make to the receiver. The stack will never be able to re-a=
ssemble the packet and now framing sync is lost.</div><div><br></div><div>A=
t this point ANY data consumed from the initial frame header and data which=
 was received must ALSO be dis-guarded but there is NO WAY for the server t=
o indicate this to the client... (This is why UDP is commonly used, you get=
 what you get and you don&#39;t what you don&#39;t)</div><div><br></div><di=
v>There are a lot of articles outlining why TCP and RTP don&#39;t get along=
 mostly citing the overhead of re-transmissions so with Rtsp you think we w=
ould have attempted to solve this not make it worse with bad encapsulation.=
</div><div><br></div><div>Something needs to be done about this because it&=
#39;s also a security concern, e.g. if a client were to send a rtcp packet =
to the server which is very larger and contains no data he could attempt to=
 exhaust the resources of that server (if they didn&#39;t monitor their rtc=
p bandwidth properly) or at least force a higher amount of traffic.</div><d=
iv><br></div><div>So, information needs to be clear that there is no such t=
hing as a packet of less then 8 bytes under rtcp and 16 bytes under rtp. (U=
nless compression is being used; ROHC or otherwise)</div><div><br></div><di=
v>The null packet or any packet under 16 bytes would used for &#39;spacing&=
#39; not a &#39;unknown&#39; context, especially when I can have 255 channe=
ls, what unknown context am I going to use then?</div><div><br></div><div>T=
hat is 4 octets for the `$` header, and the rest for the the packet header =
which can then be inspected to be the same version, payloadtype and ssrc as=
 required by the client.</div><div><br></div><div>This prevents a client wh=
o may also send a &quot;GET_PARAMETER&quot; under interleaved transport wit=
h weird headers and a body to attempt underflow also which is something the=
 current specification does nothing to protect against.</div><div><br></div=
><div>&quot;GET_PARAMATER rtsp://someuri/ RTSP/1.0\r\nCSeq:1\r\nDate: xx:xx=
:xx\r\nContent-Length:24\r\n$UserAgent $009\r\n$\0\0\aRTSP/1.$\0\0\r\n\r\nD=
atawith$IsNotAGoodIdea!\0\0&quot;<br></div><div><br></div><div>This would a=
llow applications to still take note of when a large frame was seen but not=
 be forced to act upon it and potentially lose data, and depending on their=
 implementation allow remote code execution.</div><div><br></div><div>I urg=
e the committee to seriously look into these issues as they can have a larg=
e impact.</div><div><br></div><div><a href=3D"https://isecpartners.github.i=
o/fuzzing/vulnerabilities/2013/12/30/vlc-vulnerability.html" target=3D"_bla=
nk">https://isecpartners.github.io/fuzzing/vulnerabilities/2013/12/30/vlc-v=
ulnerability.html</a></div><div><br></div><div>VLC seems protected against =
overflow after this but with some testing I have determined that not only V=
LC but other servers and clients are vulnerable to underflow this way as we=
ll making it both a server and client issue.</div><div><br></div><div>I hav=
e more notes in my implementation @=C2=A0<a href=3D"https://net7mma.codeple=
x.com/SourceControl/latest#Rtp/RtpClient.cs" target=3D"_blank">https://net7=
mma.codeplex.com/SourceControl/latest#Rtp/RtpClient.cs</a> if your interest=
ed, it relates to one issue I saw where even though frame length was good o=
ther data in the packet was invalid such as the &#39;Extension&#39; or the =
&#39;Length In Words Minus 1&#39; or the ssrc etc.</div><div><br></div><div=
>Hopefully I didn&#39;t banter to much, it&#39;s rather late.</div><div><br=
></div><div>As for my other &#39;issues&#39; / errata for RFC2435 has anyth=
ing been determined on them?</div><div><br></div><div>What about the one fo=
r RFC3550, has anyone sat down to do the math on that one yet?</div><div><b=
r></div><div>Thanks again for your time and response and have a Happy New Y=
ear if I don&#39;t hear back by then!</div><div><br></div><div>Sincerely,</=
div><div>Julius Friedman</div><div><br></div><div><br></div></div></div></d=
iv><div><div class=3D"h5"><div><div><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Tue, Dec 30, 2014 at 3:33 PM, Dale R. Worley <span di=
r=3D"ltr">&lt;<a href=3D"mailto:worley@ariadne.com" target=3D"_blank">worle=
y@ariadne.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span=
>Julius Friedman &lt;<a href=3D"mailto:juliusfriedman@gmail.com" target=3D"=
_blank">juliusfriedman@gmail.com</a>&gt; writes:<br>
&gt;=C2=A0 Transport=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=3D=C2=A0 =C2=
=A0 &quot;Transport&quot; &quot;:&quot;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01\#transport-spec<br>
<br>
</span>In a few places, RFC 2326 seems to use &quot;\#&quot; in place of &q=
uot;#&quot;.=C2=A0 There<br>
doesn&#39;t seem to be any documentation for this.=C2=A0 There seems to be =
other<br>
peculiar punctuation as well, including &quot;\$&quot; and &quot;$&#39;$&qu=
ot;.<br>
<span><br>
&gt; Since &#39;source&#39; is not listed I don&#39;t know the syntax, I as=
sumed it to<br>
&gt; be an &quot;IPAddress&quot; however the text sates &quot;address&quot;=
 so I imagine if I<br>
&gt; found a &#39;source=3D<a href=3D"http://1.2.3.4:1554" target=3D"_blank=
">1.2.3.4:1554</a>&#39; that would be valid however I want to<br>
&gt; make sure since there isn&#39;t any syntax specified in the RFC.<br>
<br>
</span>It&#39;s not clear to me that there *is* a &quot;source=3D&quot; par=
ameter for the<br>
Transport header.=C2=A0 Yes, there is prose describing source as a datum, b=
ut<br>
there&#39;s no BNF for a corresponding parameter, and a quick search doesn&=
#39;t<br>
turn up any instance of &quot;Transport:=C2=A0 ...source=3D...&quot; in any=
 RFC or I-D.<br>
<br>
However, &quot;source=3D&quot; is shown in<br>
<a href=3D"http://heim.ifi.uio.no/~meccano/reflector/smallclient.html" targ=
et=3D"_blank">http://heim.ifi.uio.no/~meccano/reflector/smallclient.html</a=
><br>
<span><br>
&gt; Also I would wonder is there any restriction on specifying a port or<b=
r>
&gt; address range also ? e.g. &#39;source=3D<a href=3D"http://1.2.3.4/3212=
02/2" target=3D"_blank">1.2.3.4/321202/2</a>&#39;<br>
<br>
</span>Well, I see &quot;parameter =3D [...] &quot;;&quot; &quot;destinatio=
n&quot; [ &quot;=3D&quot; address ]&quot;, and<br>
<br>
=C2=A0 =C2=A0address=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=3D=C2=
=A0 =C2=A0 host<br>
<br>
=C2=A0 =C2=A0host=C2=A0 =C2=A0 =C2=A0 =3D=C2=A0 =C2=A0&lt;A legal Internet =
host domain name of IP address<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(in dotted de=
cimal form), as defined by Section 2.1<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0of RFC 1123 \=
cite{rfc1123}&gt;<br>
<br>
so it looks like &lt;address&gt; cannot specifiy an address range or a port=
.<br>
I&#39;d expect the port to be specified by the &quot;client_port&quot; and<=
br>
&quot;server_port&quot; parameters.<br>
<br>
(BTW, it looks to me like the first &quot;of&quot; in the definition of &lt=
;host&gt;<br>
should be &quot;or&quot;.)<br>
<span><br>
&gt; I believe there was a similar issue with Rtp-Info headers which was<br=
>
&gt; fixed in &#39;biz&#39; however this among other issues were not addres=
sed and<br>
&gt; I am wondering if any other updates will be made to this RFC before<br=
>
&gt; 2.0 Draft is finalized.<br>
<br>
</span>An RFC is never &quot;updated&quot;, although it can be obsoleted by=
 a later RFC<br>
that entirely replaces it.<br>
<span><font color=3D"#888888"><br>
Dale<br>
</font></span></blockquote></div><br></div>
</div></div></div></div></div><br></div>
</blockquote></div><br></div>

--e89a8fb208e8d506c0050bd9add5--


From harryrat@gmx.de  Mon Jan  5 06:20:21 2015
Return-Path: <harryrat@gmx.de>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4E0C1A8851 for <avt@ietfa.amsl.com>; Mon,  5 Jan 2015 06:20:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.524
X-Spam-Level: **
X-Spam-Status: No, score=2.524 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FREEMAIL_FROM=0.001, GB_SUMOF=1, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4XhqlyUB70_z for <avt@ietfa.amsl.com>; Mon,  5 Jan 2015 06:20:20 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D3371A8850 for <avt@ietf.org>; Mon,  5 Jan 2015 06:20:20 -0800 (PST)
Received: from [84.246.251.221] by 3capp-gmx-bs11.server.lan (via HTTP); Mon, 5 Jan 2015 15:20:17 +0100
MIME-Version: 1.0
Message-ID: <trinity-db1651cc-9514-495d-b11b-281dc69b056c-1420467617692@3capp-gmx-bs11>
From: "Harald Radke" <harryrat@gmx.de>
To: avt@ietf.org
Content-Type: text/html; charset=UTF-8
Date: Mon, 5 Jan 2015 15:20:17 +0100
Importance: normal
Sensitivity: Normal
X-Priority: 3
X-Provags-ID: V03:K0:+nG7XRDAzPdT/lFvR0ZE+0hWXXVgDlKNF/sMjLg6wie 6oT83vm48iK1QSG9DjERcvxaIKgVwfZMM4NH5m5bFl2pyewguJ n5EcDxKo5+I2L4ssvgY6pWbolWCWyX71xVrjIAw+bpFffRHeGB Wr7Hc6LW3bOustJyBNCPo43a26z9fttp2eCZ+J5oPkkzGSrGcy CUvvpO8mJcluD4BlYM4BQl8cfzHtmiEepyNVbLe24b3zuY71MD enUPwdmTtlOsLFPCJknyBoXDL22xpEb+DZFrAKMYYOKtLn+dd9 HB/MJU=
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/Mlok7hTmbxHUVRA1FVnXt1aYW4A
Subject: [AVTCORE] RFC4566 - understanding maxptime
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jan 2015 14:26:07 -0000

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi all,</div>

<div>&nbsp;</div>

<div>I have slight troubles to understand the RFC4566 definition of the maxptime attribute</div>

<div>&nbsp;</div>

<div>(if this mailing list is not the right place to ask questions to understand RFCs, just to discuss them, I&nbsp; am sorry, just tell me and I wont bother you any further).</div>

<div>&nbsp;</div>

<div>RFC4566 states:</div>

<div>&nbsp;</div>

<div>a=maxptime:&lt;maximum packet time&gt;<br/>
This gives the maximum amount of media that can be encapsulated<br/>
in each packet, expressed as time in milliseconds. The time<br/>
SHALL be calculated as the sum of the time the media present in<br/>
the packet represents. [...]</div>

<div>&nbsp;</div>

<div>1) I kinda get the first sentence, but what does that second sentence actually mean? I kinda have problems understanding the SUM</div>

<div>statement. Does that &quot;only&quot; mean that in case of multiple frames in one packet that all frame durations are summed up? I wonder because the ptime definition does not contain a similar statement.</div>

<div>&nbsp;</div>

<div>2) Actually somebody already asked a similar question some time (actually years) ago, actually the difference between ptime and maxptime, the answer was:</div>

<div>&nbsp;</div>

<div><tt>&gt;The &quot;a=ptime:&quot; attribute is a hint to the encoder on the preferred packetisation interval for the media. The encoder may follow the hint, or it may vary the packetisation &gt;interval up to the value indicated by &quot;a=maxptime:&quot;. The receiver is expected to be able to decode any reasonable packetisation.</tt><br/>
&nbsp;</div>

<div>a)is the receiver expected to decode ANY packetisation? (e.g. ptime=20, maxptime=40 -&gt; incoming RTP packets of the stream might contain payloads worth of any length between 20 and 40ms, in case of sample based codecs with sample duration granularity?)</div>

<div>&nbsp;</div>

<div>b) must the receiver be able to handle varying packetisation during a session? that is receiving RTP packets with different payload lengths and different interarrival times or does &quot;vary&quot; just mean&nbsp; that the sender &quot;selects&quot; one packetisation interval between ptime and maxptime at the beginningbut keeps it constant during the session?</div>

<div>&nbsp;</div>

<div>Thank you very much and regards,</div>

<div>&nbsp;</div>

<div>Harry</div></div></body></html>


From nobody Mon Jan  5 06:40:56 2015
Return-Path: <alan.d.clark@telchemy.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEEBD1A889A for <avt@ietfa.amsl.com>; Mon,  5 Jan 2015 06:40:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.299
X-Spam-Level: 
X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_SUMOF=1, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uKLvwYUiOl2w for <avt@ietfa.amsl.com>; Mon,  5 Jan 2015 06:40:52 -0800 (PST)
Received: from omx.cbeyond.com (omx.cbeyond.com [50.20.30.10]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D7431A8897 for <avt@ietf.org>; Mon,  5 Jan 2015 06:40:52 -0800 (PST)
X-SBRS: -4.0
X-HAT: Sender Group POORREP_BLACKLIST, Policy $SBRSPOOR applied.
X-Hostname: omx01bay.sys.cbeyond.net
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq4KAAyiqlRLi1xcPGdsb2JhbABcgkNDUljGFgEJhW0EAgKBBxcBAQEBAQYBAQEBODuEDQEBBAEBASQvGAoRCw4KCRYPCQMCAQIBFRIKFAYBDAYCAQGIKAUIvFcBAQEBBgEBAQEaBIxHgzeEKQWJS58NgjGBfSAxgkMBAQE
X-IPAS-Result: Aq4KAAyiqlRLi1xcPGdsb2JhbABcgkNDUljGFgEJhW0EAgKBBxcBAQEBAQYBAQEBODuEDQEBBAEBASQvGAoRCw4KCRYPCQMCAQIBFRIKFAYBDAYCAQGIKAUIvFcBAQEBBgEBAQEaBIxHgzeEKQWJS58NgjGBfSAxgkMBAQE
X-IronPort-AV: E=Sophos;i="5.07,700,1413259200";  d="scan'208,217";a="151399961"
Received: from 75-139-92-92.dhcp.spbg.sc.charter.com (HELO Alans-MacBook-Pro.local) ([75.139.92.92]) by omx.cbeyond.com with ESMTP/TLS/DHE-RSA-AES128-SHA; 05 Jan 2015 09:40:51 -0500
Message-ID: <54AAA272.5060204@telchemy.com>
Date: Mon, 05 Jan 2015 09:40:50 -0500
From: Alan Clark <alan.d.clark@telchemy.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Harald Radke <harryrat@gmx.de>, avt@ietf.org
References: <trinity-db1651cc-9514-495d-b11b-281dc69b056c-1420467617692@3capp-gmx-bs11>
In-Reply-To: <trinity-db1651cc-9514-495d-b11b-281dc69b056c-1420467617692@3capp-gmx-bs11>
Content-Type: multipart/alternative; boundary="------------010407060203090601010701"
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/lfChW2CjWD7YpP6s5nE4hnOqEJ0
Subject: Re: [AVTCORE] RFC4566 - understanding maxptime
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jan 2015 14:40:54 -0000

This is a multi-part message in MIME format.
--------------010407060203090601010701
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Hi Harry

We have definitely seen implementations in the field that dynamically 
varied the media time encoded within an RTP packet during a single 
session and the associate inter-arrival times; we've also built systems 
that do this for network test purposes.

One example we saw in a mobile network varied the number of 10ms encoded 
voice frames that were contained within a single RTP packet to between 1 
and 4.  I don't recall the SDP that was used to negotiate this however 
the receiver had to process variable duration frames.

Regards

Alan


On 1/5/15 9:20 AM, Harald Radke wrote:
> Hi all,
> I have slight troubles to understand the RFC4566 definition of the 
> maxptime attribute
> (if this mailing list is not the right place to ask questions to 
> understand RFCs, just to discuss them, I  am sorry, just tell me and I 
> wont bother you any further).
> RFC4566 states:
> a=maxptime:<maximum packet time>
> This gives the maximum amount of media that can be encapsulated
> in each packet, expressed as time in milliseconds. The time
> SHALL be calculated as the sum of the time the media present in
> the packet represents. [...]
> 1) I kinda get the first sentence, but what does that second sentence 
> actually mean? I kinda have problems understanding the SUM
> statement. Does that "only" mean that in case of multiple frames in 
> one packet that all frame durations are summed up? I wonder because 
> the ptime definition does not contain a similar statement.
> 2) Actually somebody already asked a similar question some time 
> (actually years) ago, actually the difference between ptime and 
> maxptime, the answer was:
> >The "a=ptime:" attribute is a hint to the encoder on the preferred 
> packetisation interval for the media. The encoder may follow the hint, 
> or it may vary the packetisation >interval up to the value indicated 
> by "a=maxptime:". The receiver is expected to be able to decode any 
> reasonable packetisation.
> a)is the receiver expected to decode ANY packetisation? (e.g. 
> ptime=20, maxptime=40 -> incoming RTP packets of the stream might 
> contain payloads worth of any length between 20 and 40ms, in case of 
> sample based codecs with sample duration granularity?)
> b) must the receiver be able to handle varying packetisation during a 
> session? that is receiving RTP packets with different payload lengths 
> and different interarrival times or does "vary" just mean  that the 
> sender "selects" one packetisation interval between ptime and maxptime 
> at the beginningbut keeps it constant during the session?
> Thank you very much and regards,
> Harry
>
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


--------------010407060203090601010701
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Harry<br>
    <br>
    We have definitely seen implementations in the field that
    dynamically varied the media time encoded within an RTP packet
    during a single session and the associate inter-arrival times; we've
    also built systems that do this for network test purposes. <br>
    <br>
    One example we saw in a mobile network varied the number of 10ms
    encoded voice frames that were contained within a single RTP packet
    to between 1 and 4.  I don't recall the SDP that was used to
    negotiate this however the receiver had to process variable duration
    frames.  <br>
    <br>
    Regards<br>
    <br>
    Alan<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 1/5/15 9:20 AM, Harald Radke wrote:<br>
    </div>
    <blockquote
cite="mid:trinity-db1651cc-9514-495d-b11b-281dc69b056c-1420467617692@3capp-gmx-bs11"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div style="font-family: Verdana;font-size: 12.0px;">
        <div>Hi all,</div>
        <div> </div>
        <div>I have slight troubles to understand the RFC4566 definition
          of the maxptime attribute</div>
        <div> </div>
        <div>(if this mailing list is not the right place to ask
          questions to understand RFCs, just to discuss them, I  am
          sorry, just tell me and I wont bother you any further).</div>
        <div> </div>
        <div>RFC4566 states:</div>
        <div> </div>
        <div>a=maxptime:&lt;maximum packet time&gt;<br>
          This gives the maximum amount of media that can be
          encapsulated<br>
          in each packet, expressed as time in milliseconds. The time<br>
          SHALL be calculated as the sum of the time the media present
          in<br>
          the packet represents. [...]</div>
        <div> </div>
        <div>1) I kinda get the first sentence, but what does that
          second sentence actually mean? I kinda have problems
          understanding the SUM</div>
        <div>statement. Does that "only" mean that in case of multiple
          frames in one packet that all frame durations are summed up? I
          wonder because the ptime definition does not contain a similar
          statement.</div>
        <div> </div>
        <div>2) Actually somebody already asked a similar question some
          time (actually years) ago, actually the difference between
          ptime and maxptime, the answer was:</div>
        <div> </div>
        <div><tt>&gt;The "a=ptime:" attribute is a hint to the encoder
            on the preferred packetisation interval for the media. The
            encoder may follow the hint, or it may vary the
            packetisation &gt;interval up to the value indicated by
            "a=maxptime:". The receiver is expected to be able to decode
            any reasonable packetisation.</tt><br>
           </div>
        <div>a)is the receiver expected to decode ANY packetisation?
          (e.g. ptime=20, maxptime=40 -&gt; incoming RTP packets of the
          stream might contain payloads worth of any length between 20
          and 40ms, in case of sample based codecs with sample duration
          granularity?)</div>
        <div> </div>
        <div>b) must the receiver be able to handle varying
          packetisation during a session? that is receiving RTP packets
          with different payload lengths and different interarrival
          times or does "vary" just mean  that the sender "selects" one
          packetisation interval between ptime and maxptime at the
          beginningbut keeps it constant during the session?</div>
        <div> </div>
        <div>Thank you very much and regards,</div>
        <div> </div>
        <div>Harry</div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Audio/Video Transport Core Maintenance
<a class="moz-txt-link-abbreviated" href="mailto:avt@ietf.org">avt@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/avt">https://www.ietf.org/mailman/listinfo/avt</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------010407060203090601010701--


From nobody Mon Jan  5 07:06:02 2015
Return-Path: <sperreault@jive.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E60F1A8AC3 for <avt@ietfa.amsl.com>; Mon,  5 Jan 2015 07:05:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hB7huTefTKWu for <avt@ietfa.amsl.com>; Mon,  5 Jan 2015 07:05:57 -0800 (PST)
Received: from mail-lb0-f171.google.com (mail-lb0-f171.google.com [209.85.217.171]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FCC21A8A54 for <avt@ietf.org>; Mon,  5 Jan 2015 07:05:54 -0800 (PST)
Received: by mail-lb0-f171.google.com with SMTP id w7so17834234lbi.2 for <avt@ietf.org>; Mon, 05 Jan 2015 07:05:52 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=hKJLQI835mzM5EvX6W0+iM5bM1t0C7T1j1nh1+5dxxE=; b=VL8J8Oktb/0To9QAKNboZFE1LOiWcwN3b9yhKabsSD62eGBoYQAhg6wT+JJpVJ6Fo0 d+dv11oiGFVQ3muPfx2S2MMWWe1HmRMBqRNOuHL9K8YRF1FzpD7/KxoJzkKxVUnYuFJw 6aMykWV/kFRVOSpIlFPBDkwgVziU5/n5JEBnuEb/cq/U0s0RSzpCu12ho6UXrYZInADy ab55cB3NK7ZrDOdXardMiFfmo4zz+L0wm49Pv7/QOw2JWhyvV+rxa3NoC98lErzXa87a JXntFPQZVYiYtXO7chxuPM077QORaYixfx0PnF8qAEM+dkTTCBvC+0HF18vMBYUTzNNI yVVQ==
X-Gm-Message-State: ALoCoQltf5b9FIkA/1J7IKESAmr9lKt34CyaznR1013/Jy9W0rgcr+99bmNei8MLFKdb3GnwkDA7
MIME-Version: 1.0
X-Received: by 10.112.41.234 with SMTP id i10mr94283424lbl.25.1420470352580; Mon, 05 Jan 2015 07:05:52 -0800 (PST)
Received: by 10.25.84.145 with HTTP; Mon, 5 Jan 2015 07:05:52 -0800 (PST)
In-Reply-To: <trinity-db1651cc-9514-495d-b11b-281dc69b056c-1420467617692@3capp-gmx-bs11>
References: <trinity-db1651cc-9514-495d-b11b-281dc69b056c-1420467617692@3capp-gmx-bs11>
Date: Mon, 5 Jan 2015 10:05:52 -0500
Message-ID: <CANO7kWDKHxZyup=xW3w2H0FpA7TuL2706SeYXS7fSqZ1LP79QA@mail.gmail.com>
From: Simon Perreault <sperreault@jive.com>
To: Harald Radke <harryrat@gmx.de>
Content-Type: multipart/alternative; boundary=001a1134593cc7a9ff050be906ef
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/JP4O2CuNNJbMzXOd1IgJVtzEPW4
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] RFC4566 - understanding maxptime
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jan 2015 15:05:59 -0000

--001a1134593cc7a9ff050be906ef
Content-Type: text/plain; charset=UTF-8

On Mon, Jan 5, 2015 at 9:20 AM, Harald Radke <harryrat@gmx.de> wrote:

> 2) Actually somebody already asked a similar question some time (actually
> years) ago, actually the difference between ptime and maxptime, the answer
> was:
>
> >The "a=ptime:" attribute is a hint to the encoder on the preferred
> packetisation interval for the media. The encoder may follow the hint, or
> it may vary the packetisation >interval up to the value indicated by
> "a=maxptime:". The receiver is expected to be able to decode any reasonable
> packetisation.
>
> a)is the receiver expected to decode ANY packetisation? (e.g. ptime=20,
> maxptime=40 -> incoming RTP packets of the stream might contain payloads
> worth of any length between 20 and 40ms, in case of sample based codecs
> with sample duration granularity?)
>
b) must the receiver be able to handle varying packetisation during a
> session? that is receiving RTP packets with different payload lengths and
> different interarrival times or does "vary" just mean  that the sender
> "selects" one packetisation interval between ptime and maxptime at the
> beginningbut keeps it constant during the session?
>

My own policy regarding this is:

- I will not spend any effort dealing with crazy ptime bullshit (e.g., 21).
If the codec implementation I use works on byte boundaries, you're lucky,
but if it works on e.g. 10ms blocks then just too bad.
- Other than that, I don't really care about ptime. It all just goes into
one big queue. So you can vary ptimes as much as you like, you can ignore
my SDP, etc. Just don't go crazy.

Simon

--001a1134593cc7a9ff050be906ef
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mon, Jan 5, 2015 at 9:20 AM, Harald Radke <span dir=3D"ltr">&lt;<a href=
=3D"mailto:harryrat@gmx.de" target=3D"_blank">harryrat@gmx.de</a>&gt;</span=
> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-s=
tyle:solid;padding-left:1ex"><div>2) Actually somebody already asked a simi=
lar question some time (actually years) ago, actually the difference betwee=
n ptime and maxptime, the answer was:</div>

<div>=C2=A0</div>

<div><tt>&gt;The &quot;a=3Dptime:&quot; attribute is a hint to the encoder =
on the preferred packetisation interval for the media. The encoder may foll=
ow the hint, or it may vary the packetisation &gt;interval up to the value =
indicated by &quot;a=3Dmaxptime:&quot;. The receiver is expected to be able=
 to decode any reasonable packetisation.</tt><br>
=C2=A0</div>

<div>a)is the receiver expected to decode ANY packetisation? (e.g. ptime=3D=
20, maxptime=3D40 -&gt; incoming RTP packets of the stream might contain pa=
yloads worth of any length between 20 and 40ms, in case of sample based cod=
ecs with sample duration granularity?)</div></blockquote><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<div>b) must the receiver be able to handle varying packetisation during a =
session? that is receiving RTP packets with different payload lengths and d=
ifferent interarrival times or does &quot;vary&quot; just mean=C2=A0 that t=
he sender &quot;selects&quot; one packetisation interval between ptime and =
maxptime at the beginningbut keeps it constant during the session?</div></b=
lockquote></div><div><br class=3D"">My own policy regarding this is:</div><=
div><br></div><div>- I will not spend any effort dealing with crazy ptime b=
ullshit (e.g., 21). If the codec implementation I use works on byte boundar=
ies, you&#39;re lucky, but if it works on e.g. 10ms blocks then just too ba=
d.</div><div>- Other than that, I don&#39;t really care about ptime. It all=
 just goes into one big queue. So you can vary ptimes as much as you like, =
you can ignore my SDP, etc. Just don&#39;t go crazy.</div><div><br></div><d=
iv>Simon</div></div></div>

--001a1134593cc7a9ff050be906ef--


From nobody Mon Jan  5 19:52:50 2015
Return-Path: <worley@alum.mit.edu>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C932D1A0E10 for <avt@ietfa.amsl.com>; Mon,  5 Jan 2015 19:52:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lEu1fWDV4itR for <avt@ietfa.amsl.com>; Mon,  5 Jan 2015 19:52:42 -0800 (PST)
Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB2541A0AF8 for <avt@ietf.org>; Mon,  5 Jan 2015 19:52:41 -0800 (PST)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-05v.sys.comcast.net with comcast id cTsY1p0062Bo0NV01Tshos; Tue, 06 Jan 2015 03:52:41 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-ch2-05v.sys.comcast.net with comcast id cTsg1p00D1KKtkw01Tsg9e; Tue, 06 Jan 2015 03:52:41 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id t063qd9V031524; Mon, 5 Jan 2015 22:52:39 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id t063qdWY031521; Mon, 5 Jan 2015 22:52:39 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Julius Friedman <juliusfriedman@gmail.com>
In-Reply-To: <CACFvNHXhFQe2CEKsv4q637SoGa-vKuhztN+a1ywK1ewU_Sa6KA@mail.gmail.com> (juliusfriedman@gmail.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Mon, 05 Jan 2015 22:52:39 -0500
Message-ID: <87d26sefaw.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1420516361; bh=A3IB4do+hM7fWaKDpNXjkBeylTWehpBeJCuDNia+t1w=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=m8HE4ApaCd3CDkXSolrwMetBz/9qmhQ66eou9zOaqlo4LgfihgYwiPoXldV1L88Zx uJaE2mVHLf77tXih32k1tx+eFKsH31rg/+tFg2OT2omxYYrRk1y9+SB7eTrH+N1El3 /i+dcOQop6dWdHFwv75B09Ax1X01WKxcSoM3xMH7+WTmWLG3gCJ8WYXHjtcEwI15qr 6HKK0q8Rxh3GuLAMBTnwi5hm5C4tkL5bgS3AIgHeuH8PinHyAsYsOEl1pCzz5/6ANU oelSDmey27mia9ZmMoZL9oKpYJTnkYJxQ47Nu60Fa24rqnsQp2AY0fgKqB3FOnau9l rJILKv+rhp4zA==
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/-Np6T28Q9K8mvFOO15hcacAn7_w
Cc: avt@ietf.org, mmusic@ietf.org
Subject: Re: [AVTCORE] Question
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 03:52:44 -0000

Julius Friedman <juliusfriedman@gmail.com> writes:
> I would like to address your response:
>
> "In any case, why would we want to prevent seeking on a stored media
> object?  I can see why if the media is an un-stored media stream, but in
> that case, the software likely doesn't know the total length that the
> media will have."
>
> I will justify how "likely" this is as follows:
>
> 1) A Live 10 minute `media` which has been playing for 3 minutes, leaving
> me 7 minutes in play but unable to seek.
>    a) If the stream was stored or recorded this obviously wouldn't be an
> issue

But how would we know that the media is 10 minutes long if it was not
already stored?  If it was truly live, we'd only know that it was
*scheduled* to be 10 minutes long, not that it will actually *be* 10
minutes long.

> 2) I have a server which requires authorization to seek but not to play.

Why would we want to support that?

> 3) I am a client and I have started playing and 'PAUSE' is not supported
>
> 4) I am a server re-streaming from a server where "Range" is not supported

I'm no expert in RTSP, but my understanding is that these two situations
are only expected to happen when the media is truly live, that is, the
server does not know how long the media will be.

> "Perhaps referring to the mailing list discussion for this RFC would
> reveal the answer."
>
> Which mailing list is that? 'mmusic' they have also been addressed, several
> times. I never get a response from them.

I assume you mean "I have asked before on mmusic and received no
response."  Perhaps nobody else cares about the proposed capability?

I mean the mailing list discussion surrounding this document when it was
made an RFC.  (Better, look up the Internet-Draft name and refer to the
appropriate mailing list archive for the time when the I-D was being
discussed.)

Dale


From nobody Mon Jan  5 19:59:31 2015
Return-Path: <paulej@packetizer.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF5F31A19EC for <avt@ietfa.amsl.com>; Mon,  5 Jan 2015 19:59:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.002
X-Spam-Level: 
X-Spam-Status: No, score=-1.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fMUTKF2d0s6S for <avt@ietfa.amsl.com>; Mon,  5 Jan 2015 19:59:27 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF0661A07BC for <avt@ietf.org>; Mon,  5 Jan 2015 19:59:26 -0800 (PST)
Received: from [192.168.1.20] (cpe-098-027-048-015.nc.res.rr.com [98.27.48.15]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id t063xHol032541 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 5 Jan 2015 22:59:17 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1420516757; bh=iLAotHzDP1TCkLTyKhGU/Nxn1FN3Zh8IPpwAQekkyIs=; h=From:To:Subject:Cc:Date:Message-Id:In-Reply-To:Reply-To: Mime-Version:Content-Type:Content-Transfer-Encoding; b=uZ8uxQ2kyydhTE5cbr6rPazS8HP0ElKY4KTJ6GsIFZg1mTAE8zuV4eM9muW3I4x7O Z5aOhT/WESx+zgGf9vEPEnbwKKFcurT3I3u68pnasN61tHUxm3jhcO0kNXFoigSGyD TNhxTrtF/ZyK6jupowTgUmcUaIsw4VbLIhqRxhhc=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "Colin Perkins" <csp@csperkins.org>
Date: Tue, 06 Jan 2015 03:59:34 +0000
Message-Id: <em92119b83-b564-44c1-a334-2db66ed4dc9f@sydney>
In-Reply-To: <F86983B9-4022-4971-BEA7-3EFE995C496C@csperkins.org>
User-Agent: eM_Client/6.0.21034.0
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/mTcg5YGJFIXuYB93FMdF9UwKNvA
Cc: Marc Petit-Huguenin <marc@petit-huguenin.org>, "avt@ietf.org WG" <avt@ietf.org>
Subject: Re: [AVTCORE] Comments on draft-petithuguenin-avtcore-rfc5764-mux-fixes
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 03:59:30 -0000

  Colin,

Thanks for informing me of that. There is a difference in what is=20
proposed there vs. what I propose below. The shim in the draft makes=20
that first word ("Session ID Layer") look like an RTP packet. Depending=20
on the value of the "reserved" bits, this could cause a conflict with=20
other protocols already multiplexed. But, I can appreciate that this=20
could be addressed easily.

Clearly, I wasn't aiming to have something that resembles an RTP packet,=
=20
since other protocols being multiplexed don't look like them, either.=20
There is already a multiplexing layer in stacks to handle DTLS, STUN,=20
and RTP packets. I wanted something that would be one more addition that=
=20
could be more generic.

I guess the important question is why the WG wasn't keen on the idea?=20
Was this perhaps presented just a little early? I can already see some=20
utility in multiplexing multiple DTLS connections, which is presently=20
not possible. And, I'm sure there will be other protocols in the future.=
=20
So, I'm wondering if we ought to revisit this topic. Is that even an=20
option or is the door closed on this topic?

Paul

------ Original Message ------
From: "Colin Perkins" <csp@csperkins.org>
To: "Paul E. Jones" <paulej@packetizer.com>
Cc: "avt@ietf.org WG" <avt@ietf.org>; marcph@getjive.com
Sent: 12/23/2014 4:45:38 AM
Subject: Re: [AVTCORE] Comments on=20
draft-petithuguenin-avtcore-rfc5764-mux-fixes

>Paul,
>
>I agree that some sort of explicit demultiplexing shim would solve a=20
>lot of problems, and would have addressed many of the signalling issues=
=20
>WebRTC has exposed in this space. Our proposal was=20
>draft-westerlund-avtcore-transport-multiplexing-07. The working group=20
>didn=E2=80=99t seem keen on the idea, however.
>
>Colin
>
>
>
>
>On 20 Dec 2014, at 02:17, Paul E. Jones <paulej@packetizer.com> wrote:
>
>>  AVT,
>>
>>  While the issues raised in the rfc5764-mix-fixes draft are valid, I'm=
=20
>>curious if consideration has been given to address multiplexing more=20
>>generally? Years ago, if anyone suggested multiplexing STUN, DTLS,=20
>>TURN, along with RTP and RTCP, it wouldn't have been met with much=20
>>enthusiasm. Now, we are multiplexing everything over a single port. I=20
>>appreciate the reason, but it feel like this is a delicate balancing=20
>>act and it imposes restrictions on existing protocols and will impose=20
>>restrictions on future protocols to allow this model to continue=20
>>as-is.
>>
>>  Since multiplexing over a single port is now considered legitimate,=20
>>why not allocate a code point (e.g., 0x04) to be one dedicated for=20
>>multiplexing? I'm not suggesting we change what is already defined,=20
>>but rather to introduce a new code point explicitly intended to=20
>>facilitate multiplexing in such a way as to avoid having the delicate=20
>>balancing act of ensuring that values do not conflict. Such a scheme=20
>>could also be used to allow for multiple instances of the same=20
>>protocol (e.g., multiple DTLS connections) to be multiplexed over the=20
>>same port. Taken to an extreme, it might be possible to allow multiple=
=20
>>RTP sessions to be multiplexed over the same port. (I'm not suggesting=
=20
>>we go that far, but having that kind of flexibility would not hurt.)
>>
>>  My thinking is that if the first octet is 0x04, the receiver will=20
>>then look at the following two octets to determine how to handle the=20
>>packet. These two octets could be sub-divided into IANA-assigned=20
>>protocol identifiers and dynamically allocated values. Basically, we=20
>>would have this:
>>
>>     =20
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>      | 0x04 | protocol_identifier | muxed data follows ...
>>     =20
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>>  When the next protocol to be multiplexed is defined, we could=20
>>statically allocate a protocol_identifier value for the protocol. We=20
>>could also define SDP syntax that would allow these values to by=20
>>advertised so that protocols could be safely muxed even without a=20
>>static allocation. So, if there was a desire to have two WebRTC Data=20
>>Channels, for example, one (or both) might be multiplexed using this=20
>>scheme. Perhaps all packets related to the first might be identified=20
>>by 0x048001 and the other might be identified by 0x048002. You can=20
>>imagine how the protocol_identifiers 0x8001 and 0x8002 could be=20
>>advertised in SDP easily enough. DTLS is already used for two entirely=
=20
>>different purposes (DTLS-SRTP and WebRTC Data Channels), which forces=20
>>a violation of RFC 5764 Section 5.1.1. For that and other reasons, I=20
>>can see benefit in multiplexing DTLS-SRTP and the WebRTC Data Channel=20
>>(SCTP/DTLS) as two DTLS sessions.
>>
>>  Has there been discussion on this or is there interest in this=20
>>approach?
>>
>>  Paul
>>
>>  _______________________________________________
>>  Audio/Video Transport Core Maintenance
>>  avt@ietf.org
>>  https://www.ietf.org/mailman/listinfo/avt
>
>
>
>--
>Colin Perkins
>https://csperkins.org/
>
>
>
>


From nobody Tue Jan  6 06:17:14 2015
Return-Path: <juliusfriedman@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC1BC1A6F3C; Tue,  6 Jan 2015 06:17:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3n2EuX4pRw4i; Tue,  6 Jan 2015 06:17:04 -0800 (PST)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6821F1A6F2B; Tue,  6 Jan 2015 06:17:04 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id et14so31052212pad.17; Tue, 06 Jan 2015 06:17:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=W3FR3HEVbHNYHkbC983k5xvcvxelDHzt/pOL58w/qUM=; b=RwFVdkgtVPBRnf5bqJqb9TlMO2EprrMYiXxdjtsvpiRA7DSr70AZeXea1I8TKsUVmR PuG6H17gLVBbbdxt8AU+bDvBe7ZXBGLrbKNu0AJSqRKAaIThLrREwqZfaUIExNIeAAmo ZUUlTa+9Dg3fkiFqWdTPGnR9RA7Ru7lj+QfVglNNiCNXCVydfw0VZTQgP+OGinhbIomp be3op/JrWjG70bwRL4gKWaC3PQAeBbq9pfIeUxYnKAKO2S+2prxUUZ44PzO93H53hUU1 O7vwR2Ron3epgDr6PTPfFRHGEDtTHQrdpKESGdj4hY2K77zaKSCpKRcdufEiqGvI/Bv1 3jrA==
MIME-Version: 1.0
X-Received: by 10.66.102.103 with SMTP id fn7mr138089274pab.113.1420553822524;  Tue, 06 Jan 2015 06:17:02 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Tue, 6 Jan 2015 06:17:02 -0800 (PST)
In-Reply-To: <87d26sefaw.fsf@hobgoblin.ariadne.com>
References: <CACFvNHXhFQe2CEKsv4q637SoGa-vKuhztN+a1ywK1ewU_Sa6KA@mail.gmail.com> <87d26sefaw.fsf@hobgoblin.ariadne.com>
Date: Tue, 6 Jan 2015 09:17:02 -0500
Message-ID: <CACFvNHUGDyJDKA0vpPQeKN1H4TCU_8VzuP2Y-V22Jx4XuYJW9w@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>, avt@ietf.org, mmusic@ietf.org
Content-Type: multipart/alternative; boundary=047d7bd909a0f9ddc0050bfc7550
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/abtOnvbH-lCy7uWK39WVSpofJ9Q
Subject: Re: [AVTCORE] Question
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 14:17:11 -0000

--047d7bd909a0f9ddc0050bfc7550
Content-Type: text/plain; charset=UTF-8

But how would we know that the media is 10 minutes long if it was not
already stored?  If it was truly live, we'd only know that it was
*scheduled* to be 10 minutes long, not that it will actually *be* 10
minutes long.

- In that case we don't know if tomorrow will come because it isn't
guaranteed today, lets be serious.

I have a server which is aggregating a stream which is stored, my server
doesn't store the stream.

Only authorized users can seek the stream on the server to move it in time.

The public has to watch from where it is to where it ends and know that
seeking is not supported remotely.

In such a case I know the end time and that seeking isn't supported but the
client doesn't.

This is a common task 'aggregating a stream' and SHOULD be handled, the
fact that Range infers seek-ability is for lack of a better word
`over-reaching`.

I will be adding something for this in my server and I know for a fact that
others would benefit.

That aside,

What about my questions regarding the 'source' and 'ssrc' parameters? Those
aren't proposals, those are genuine questions.

What about my questions regarding the Binary Interleaved Data? The wording
on Disabling 'Retransmission' and the 'Safe' characters '\$'  or '\#'..

As for my other 'issues' / errata for RFC2435 has anything been determined
on them?

What about the one for RFC3550, has anyone sat down to do the math on that
one yet?

I will include their questions here again and I would appreciate a single
complete and through reply.

Since the binary framing was apparently an after thought (based on
information from the drafts which show interleaved data in a 'DATA' RTSP
response) I think this was remnant from that in some way or at least that's
the best I can possibly imagine.

Why the framing octet would also be listed as a 'safe' character is beyond
me, there were several other characters / octets which definitely could
have been used e.g. 0xC3 -> 0xFF.

The fact that the document makes so many statements about ease of parsing
and then literally and figuratively destroy this concept with bad decisions
such as the framing character as well as the interesting syntax for the
markup.

I will past some of those here :

1.4 <https://tools.ietf.org/html/rfc2326#section-1.4> Protocol Properties

   RTSP has the following properties:

....

   Easy to parse:
          RTSP can be parsed by standard HTTP or MIME parsers.



...



4 <https://tools.ietf.org/html/rfc2326#section-4> RTSP Message

   RTSP is a text-based protocol and uses the ISO 10646 character set in
   UTF-8 encoding (RFC 2279 <https://tools.ietf.org/html/rfc2279>
[21]). Lines are terminated by CRLF, but
   receivers should be prepared to also interpret CR and LF by
   themselves as line terminators.

     Text-based protocols make it easier to add optional parameters in a
     self-describing manner. Since the number of parameters and the
     frequency of commands is low, processing efficiency is not a
     concern. Text-based protocols, if done carefully, also allow easy
     implementation of research prototypes in scripting languages such
     as Tcl, Visual Basic and Perl.

     The 10646 character set avoids tricky character set switching, but
     is invisible to the application as long as US-ASCII is being used.
     This is also the encoding used for RTCP. ISO 8859-1 translates
     directly into Unicode with a high-order octet of zero. ISO 8859-1
     characters with the most-significant bit set are represented as
     1100001x 10xxxxxx. (See RFC 2279
<https://tools.ietf.org/html/rfc2279> [21])

   RTSP messages can be carried over any lower-layer transport protocol
   that is 8-bit clean.

   Requests contain methods, the object the method is operating upon and
   parameters to further describe the method. Methods are idempotent,
   unless otherwise noted. Methods are also designed to require little
   or no state maintenance at the media server.



This literally becomes a nightmare when you have to reconstruct TCP
sequences.

This is only exacerbated by the fact the document allows packets up to the
maximum holding size in this mode AND specifies that packets with an
unknown context must be skipped...

Skipped how? Skipped as in past their header, past their data? Can that
text even be there?

We are talking about TCP and in such a case the data from a previous
segment was already received by the receiver and contains only some of the
data how would they skip data they have yet to receive?

I will explain why this is a security issue, Since there is no sequence
information in the binary header it must be trusted to contain valid length
values. Without inspecting the latter octets one can make no such
assumption about the type of binary data contained therein, especially if
there is no context assigned.

This if I can get a single TCP packet into a stream I can very easily
inject a lot of 'receive' space thus exponentially increasing my chances of
getting another packet into the stream.

I think that there should at the very least be a correlation between
'Block-Size' and the frame size such that frame sizes MUST NOT ever be
larger than that value if not already.

Furthermore I think that something needs to be done to specify how to deal
with nuisances such as 'more / less bytes available than indicated in
frame' especially when we also have 'Rtsp' messages which can be
interleaved at the same time in between frames (which can contain "$").

So to re-iterate my understanding of how things are in toto I have an
example I will outline below which is is a Rtsp Binary Interleaved sender
who tells a Rtsp Binary Interleaved client there is a frame of 48344 bytes
on channel 0.

The client received only 1328 bytes.

47016 bytes remain.

The client starts to receive again.

At this point there should only be the rest of the data in the frame (47016
bytes)

This data will come over several MSS sized segments, during which time the
socket may also be written to again (before the segment is transmitted to
the client).

{
    If the latter data happens to get to the receiver before the other
portions of the segment we have TCP 're-ordering' based on the sequence
number and may multiple ACK's for the early packets.

    If any data is missed we will have a re-transmission.

    The data being 'received' on the socket by the receiver coming from the
server comes from the data portion of the tcp packet which now contains
data from a previous segment.
}

The sender is now committed to sending the additional bytes as indicated
however if the sender stops sending this data or it's truncated it will
never make to the receiver. The stack will never be able to re-assemble the
packet and now framing sync is lost.

At this point ANY data consumed from the initial frame header and data
which was received must ALSO be dis-guarded but there is NO WAY for the
server to indicate this to the client... (This is why UDP is commonly used,
you get what you get and you don't what you don't)

There are a lot of articles outlining why TCP and RTP don't get along
mostly citing the overhead of re-transmissions so with Rtsp you think we
would have attempted to solve this not make it worse with bad encapsulation.

Something needs to be done about this because it's also a security concern,
e.g. if a client were to send a rtcp packet to the server which is very
larger and contains no data he could attempt to exhaust the resources of
that server (if they didn't monitor their rtcp bandwidth properly) or at
least force a higher amount of traffic.

So, information needs to be clear that there is no such thing as a packet
of less then 8 bytes under rtcp and 16 bytes under rtp. (Unless compression
is being used; ROHC or otherwise)

The null packet or any packet under 16 bytes would used for 'spacing' not a
'unknown' context, especially when I can have 255 channels, what unknown
context am I going to use then?

That is 4 octets for the `$` header, and the rest for the the packet header
which can then be inspected to be the same version, payloadtype and ssrc as
required by the client.

This prevents a client who may also send a "GET_PARAMETER" under
interleaved transport with weird headers and a body to attempt underflow
also which is something the current specification does nothing to protect
against.

"GET_PARAMATER rtsp://someuri/ RTSP/1.0\r\nCSeq:1\r\nDate:
xx:xx:xx\r\nContent-Length:24\r\n$UserAgent
$009\r\n$\0\0\aRTSP/1.$\0\0\r\n\r\nDatawith$IsNotAGoodIdea!\0\0"

This would allow applications to still take note of when a large frame was
seen but not be forced to act upon it and potentially lose data, and
depending on their implementation allow remote code execution.

I urge the committee to seriously look into these issues as they can have a
large impact in both interpretation of the standard and it's security
features.

https://isecpartners.github.io/fuzzing/vulnerabilities/2013/12/30/vlc-vulnerability.html


On Mon, Jan 5, 2015 at 10:52 PM, Dale R. Worley <worley@ariadne.com> wrote:

> Julius Friedman <juliusfriedman@gmail.com> writes:
> > I would like to address your response:
> >
> > "In any case, why would we want to prevent seeking on a stored media
> > object?  I can see why if the media is an un-stored media stream, but in
> > that case, the software likely doesn't know the total length that the
> > media will have."
> >
> > I will justify how "likely" this is as follows:
> >
> > 1) A Live 10 minute `media` which has been playing for 3 minutes, leaving
> > me 7 minutes in play but unable to seek.
> >    a) If the stream was stored or recorded this obviously wouldn't be an
> > issue
>
> But how would we know that the media is 10 minutes long if it was not
> already stored?  If it was truly live, we'd only know that it was
> *scheduled* to be 10 minutes long, not that it will actually *be* 10
> minutes long.
>
> > 2) I have a server which requires authorization to seek but not to play.
>
> Why would we want to support that?
>
> > 3) I am a client and I have started playing and 'PAUSE' is not supported
> >
> > 4) I am a server re-streaming from a server where "Range" is not
> supported
>
> I'm no expert in RTSP, but my understanding is that these two situations
> are only expected to happen when the media is truly live, that is, the
> server does not know how long the media will be.
>
> > "Perhaps referring to the mailing list discussion for this RFC would
> > reveal the answer."
> >
> > Which mailing list is that? 'mmusic' they have also been addressed,
> several
> > times. I never get a response from them.
>
> I assume you mean "I have asked before on mmusic and received no
> response."  Perhaps nobody else cares about the proposed capability?
>
> I mean the mailing list discussion surrounding this document when it was
> made an RFC.  (Better, look up the Internet-Draft name and refer to the
> appropriate mailing list archive for the time when the I-D was being
> discussed.)
>
> Dale
>

--047d7bd909a0f9ddc0050bfc7550
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"font-size:12.8000001907349px">But how would=
 we know that the media is 10 minutes long if it was not</span><br style=3D=
"font-size:12.8000001907349px"><span style=3D"font-size:12.8000001907349px"=
>already stored?=C2=A0 If it was truly live, we&#39;d only know that it was=
</span><br style=3D"font-size:12.8000001907349px"><span style=3D"font-size:=
12.8000001907349px">*scheduled* to be 10 minutes long, not that it will act=
ually *be* 10</span><br style=3D"font-size:12.8000001907349px"><span style=
=3D"font-size:12.8000001907349px">minutes long.</span><br><div><span style=
=3D"font-size:12.8000001907349px"><br></span></div><div><span style=3D"font=
-size:12.8000001907349px">- In that case we don&#39;t know if tomorrow will=
 come because it isn&#39;t guaranteed today, lets be serious.</span></div><=
div><span style=3D"font-size:12.8000001907349px"><br></span></div><div><spa=
n style=3D"font-size:12.8000001907349px">I have a server which is aggregati=
ng a stream which is stored, my server doesn&#39;t store the stream.</span>=
</div><div><span style=3D"font-size:12.8000001907349px"><br></span></div><d=
iv><span style=3D"font-size:12.8000001907349px">Only authorized users can s=
eek the stream on the server to move it in time.</span></div><div><span sty=
le=3D"font-size:12.8000001907349px"><br></span></div><div>The public has to=
 watch from where it is to where it ends and know that seeking is not suppo=
rted remotely.</div><div><br></div><div>In such a case I know the end time =
and that seeking isn&#39;t supported but the client doesn&#39;t.</div><div>=
<br></div><div>This is a common task &#39;aggregating a stream&#39; and SHO=
ULD be handled, the fact that Range infers seek-ability is for lack of a be=
tter word `over-reaching`.</div><div><br></div><div>I will be adding someth=
ing for this in my server and I know for a fact that others would benefit.<=
/div><div><br></div><div>That aside,</div><div><br></div><div>What about my=
 questions regarding the &#39;source&#39; and &#39;ssrc&#39; parameters? Th=
ose aren&#39;t proposals, those are genuine questions.</div><div><br></div>=
<div>What about my questions regarding the Binary Interleaved Data? The wor=
ding on Disabling &#39;Retransmission&#39; and the &#39;Safe&#39; character=
s &#39;\$&#39; =C2=A0or &#39;\#&#39;..</div><div><div style=3D"font-size:12=
.8000001907349px"><span style=3D"font-size:12.8000001907349px"><br></span><=
/div><div style=3D"font-size:12.8000001907349px"><span style=3D"font-size:1=
2.8000001907349px">As for my other &#39;issues&#39; / errata for RFC2435 ha=
s anything been determined on them?</span><br></div><div style=3D"font-size=
:12.8000001907349px"><br></div><div style=3D"font-size:12.8000001907349px">=
What about the one for RFC3550, has anyone sat down to do the math on that =
one yet?</div></div><div><br></div><div>I will include their questions here=
 again and I would appreciate a single complete and through reply.</div><di=
v><span style=3D"font-size:12.8000001907349px"><br></span></div><div><div s=
tyle=3D"font-size:12.8000001907349px">Since the binary framing was apparent=
ly an after thought (based on information from the drafts which show interl=
eaved data in a &#39;DATA&#39; RTSP response) I think this was remnant from=
 that in some way or at least that&#39;s the best I can possibly imagine.</=
div><div style=3D"font-size:12.8000001907349px"><br></div><div style=3D"fon=
t-size:12.8000001907349px">Why the framing octet would also be listed as a =
&#39;safe&#39; character is beyond me, there were several other characters =
/ octets which definitely could have been used e.g. 0xC3 -&gt; 0xFF.</div><=
div style=3D"font-size:12.8000001907349px"><br></div><div style=3D"font-siz=
e:12.8000001907349px">The fact that the document makes so many statements a=
bout ease of parsing and then literally and figuratively destroy this conce=
pt with bad decisions such as the framing character as well as the interest=
ing syntax for the markup.</div><div style=3D"font-size:12.8000001907349px"=
><br></div><div style=3D"font-size:12.8000001907349px">I will past some of =
those here :</div><div style=3D"font-size:12.8000001907349px"><br></div><di=
v style=3D"font-size:12.8000001907349px"><pre style=3D"white-space:pre-wrap=
;font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span sty=
le=3D"line-height:0pt;font-size:1em;font-weight:bold"><h3 style=3D"line-hei=
ght:0pt;display:inline;font-size:1em"><a name=3D"14a9f8300a80f387_section-1=
.4" href=3D"https://tools.ietf.org/html/rfc2326#section-1.4" target=3D"_bla=
nk" style=3D"color:black;text-decoration:none">1.4</a> Protocol Properties<=
/h3></span>

   RTSP has the following properties:

....

   Easy to parse:
          RTSP can be parsed by standard HTTP or MIME parsers.</pre><pre st=
yle=3D"white-space:pre-wrap;font-size:1em;margin-top:0px;margin-bottom:0px;=
color:rgb(0,0,0)"><br></pre><pre style=3D"white-space:pre-wrap;font-size:1e=
m;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre style=
=3D"white-space:pre-wrap;font-size:1em;margin-top:0px;margin-bottom:0px;col=
or:rgb(0,0,0)">...</pre><pre style=3D"white-space:pre-wrap;font-size:1em;ma=
rgin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre style=3D"wh=
ite-space:pre-wrap;font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb=
(0,0,0)"><br></pre><pre style=3D"white-space:pre-wrap;font-size:1em;margin-=
top:0px;margin-bottom:0px;color:rgb(0,0,0)"><pre style=3D"white-space:pre-w=
rap;font-size:1em;margin-top:0px;margin-bottom:0px"><span style=3D"line-hei=
ght:0pt;font-size:1em;font-weight:bold"><h2 style=3D"line-height:0pt;displa=
y:inline;font-size:1em"><a name=3D"14a9f8300a80f387_section-4" href=3D"http=
s://tools.ietf.org/html/rfc2326#section-4" target=3D"_blank" style=3D"color=
:black;text-decoration:none">4</a> RTSP Message</h2></span>

   RTSP is a text-based protocol and uses the ISO 10646 character set in
   UTF-8 encoding (<a href=3D"https://tools.ietf.org/html/rfc2279" target=
=3D"_blank">RFC 2279</a> [21]). Lines are terminated by CRLF, but
   receivers should be prepared to also interpret CR and LF by
   themselves as line terminators.

     Text-based protocols make it easier to add optional parameters in a
     self-describing manner. Since the number of parameters and the
     frequency of commands is low, processing efficiency is not a
     concern. Text-based protocols, if done carefully, also allow easy
     implementation of research prototypes in scripting languages such
     as Tcl, Visual Basic and Perl.

     The 10646 character set avoids tricky character set switching, but
     is invisible to the application as long as US-ASCII is being used.
     This is also the encoding used for RTCP. ISO 8859-1 translates
     directly into Unicode with a high-order octet of zero. ISO 8859-1
     characters with the most-significant bit set are represented as
     1100001x 10xxxxxx. (See <a href=3D"https://tools.ietf.org/html/rfc2279=
" target=3D"_blank">RFC 2279</a> [21])

   RTSP messages can be carried over any lower-layer transport protocol
   that is 8-bit clean.

   Requests contain methods, the object the method is operating upon and
   parameters to further describe the method. Methods are idempotent,
   unless otherwise noted. Methods are also designed to require little
   or no state maintenance at the media server.</pre></pre></div><div style=
=3D"font-size:12.8000001907349px"><br></div><div style=3D"font-size:12.8000=
001907349px"><br></div><div style=3D"font-size:12.8000001907349px">This lit=
erally becomes a nightmare when you have to reconstruct TCP sequences.</div=
><div style=3D"font-size:12.8000001907349px"><br></div><div style=3D"font-s=
ize:12.8000001907349px">This is only exacerbated by the fact the document a=
llows packets up to the maximum holding size in this mode AND specifies tha=
t packets with an unknown context must be skipped...</div><div style=3D"fon=
t-size:12.8000001907349px"><br></div><div style=3D"font-size:12.80000019073=
49px">Skipped how? Skipped as in past their header, past their data? Can th=
at text even be there?</div><div style=3D"font-size:12.8000001907349px"><br=
></div><div style=3D"font-size:12.8000001907349px">We are talking about TCP=
 and in such a case the data from a previous segment was already received b=
y the receiver and contains only some of the data how would they skip data =
they have yet to receive?=C2=A0</div><div style=3D"font-size:12.80000019073=
49px"><br></div><div style=3D"font-size:12.8000001907349px">I will explain =
why this is a security issue, Since there is no sequence information in the=
 binary header it must be trusted to contain valid length values. Without i=
nspecting the latter octets one can make no such assumption about the type =
of binary data contained therein, especially if there is no context assigne=
d.</div><div style=3D"font-size:12.8000001907349px"><br></div><div style=3D=
"font-size:12.8000001907349px">This if I can get a single TCP packet into a=
 stream I can very easily inject a lot of &#39;receive&#39; space thus expo=
nentially increasing my chances of getting another packet into the stream.<=
/div><div style=3D"font-size:12.8000001907349px"><br></div><div style=3D"fo=
nt-size:12.8000001907349px">I think that there should at the very least be =
a correlation between &#39;Block-Size&#39; and the frame size such that fra=
me sizes MUST NOT ever be larger than that value if not already.</div><div =
style=3D"font-size:12.8000001907349px"><br></div><div style=3D"font-size:12=
.8000001907349px">Furthermore I think that something needs to be done to sp=
ecify how to deal with nuisances such as &#39;more / less bytes available t=
han indicated in frame&#39; especially when we also have &#39;Rtsp&#39; mes=
sages which can be interleaved at the same time in between frames (which ca=
n contain &quot;$&quot;).</div><div style=3D"font-size:12.8000001907349px">=
<br></div><div style=3D"font-size:12.8000001907349px">So to re-iterate my u=
nderstanding of how things are in toto I have an example I will outline bel=
ow which is is a Rtsp Binary Interleaved sender who tells a Rtsp Binary Int=
erleaved client there is a frame of 48344 bytes on channel 0.</div><div sty=
le=3D"font-size:12.8000001907349px"><br></div><div style=3D"font-size:12.80=
00001907349px">The client received only 1328 bytes.</div><div style=3D"font=
-size:12.8000001907349px"><br></div><div style=3D"font-size:12.800000190734=
9px">47016 bytes remain.<br></div><div style=3D"font-size:12.8000001907349p=
x"><br></div><div style=3D"font-size:12.8000001907349px">The client starts =
to receive again.</div><div style=3D"font-size:12.8000001907349px"><br></di=
v><div style=3D"font-size:12.8000001907349px">At this point there should on=
ly be the rest of the data in the frame (47016 bytes)</div><div style=3D"fo=
nt-size:12.8000001907349px"><br></div><div style=3D"font-size:12.8000001907=
349px">This data will come over several MSS sized segments, during which ti=
me the socket may also be written to again (before the segment is transmitt=
ed to the client).</div><div style=3D"font-size:12.8000001907349px"><br></d=
iv><div style=3D"font-size:12.8000001907349px">{</div><div style=3D"font-si=
ze:12.8000001907349px">=C2=A0 =C2=A0 If the latter data happens to get to t=
he receiver before the other portions of the segment we have TCP &#39;re-or=
dering&#39; based on the sequence number and may multiple ACK&#39;s for the=
 early packets.</div><div style=3D"font-size:12.8000001907349px"><br></div>=
<div style=3D"font-size:12.8000001907349px">=C2=A0 =C2=A0 If any data is mi=
ssed we will have a re-transmission.</div><div style=3D"font-size:12.800000=
1907349px"><br></div><div style=3D"font-size:12.8000001907349px">=C2=A0 =C2=
=A0 The data being &#39;received&#39; on the socket by the receiver coming =
from the server comes from the data portion of the tcp packet which now con=
tains data from a previous segment.<br></div><div style=3D"font-size:12.800=
0001907349px">}</div><div style=3D"font-size:12.8000001907349px"><br></div>=
<div style=3D"font-size:12.8000001907349px">The sender is now committed to =
sending the additional bytes as indicated however if the sender stops sendi=
ng this data or it&#39;s truncated it will never make to the receiver. The =
stack will never be able to re-assemble the packet and now framing sync is =
lost.</div><div style=3D"font-size:12.8000001907349px"><br></div><div style=
=3D"font-size:12.8000001907349px">At this point ANY data consumed from the =
initial frame header and data which was received must ALSO be dis-guarded b=
ut there is NO WAY for the server to indicate this to the client... (This i=
s why UDP is commonly used, you get what you get and you don&#39;t what you=
 don&#39;t)</div><div style=3D"font-size:12.8000001907349px"><br></div><div=
 style=3D"font-size:12.8000001907349px">There are a lot of articles outlini=
ng why TCP and RTP don&#39;t get along mostly citing the overhead of re-tra=
nsmissions so with Rtsp you think we would have attempted to solve this not=
 make it worse with bad encapsulation.</div><div style=3D"font-size:12.8000=
001907349px"><br></div><div style=3D"font-size:12.8000001907349px">Somethin=
g needs to be done about this because it&#39;s also a security concern, e.g=
. if a client were to send a rtcp packet to the server which is very larger=
 and contains no data he could attempt to exhaust the resources of that ser=
ver (if they didn&#39;t monitor their rtcp bandwidth properly) or at least =
force a higher amount of traffic.</div><div style=3D"font-size:12.800000190=
7349px"><br></div><div style=3D"font-size:12.8000001907349px">So, informati=
on needs to be clear that there is no such thing as a packet of less then 8=
 bytes under rtcp and 16 bytes under rtp. (Unless compression is being used=
; ROHC or otherwise)</div><div style=3D"font-size:12.8000001907349px"><br><=
/div><div style=3D"font-size:12.8000001907349px">The null packet or any pac=
ket under 16 bytes would used for &#39;spacing&#39; not a &#39;unknown&#39;=
 context, especially when I can have 255 channels, what unknown context am =
I going to use then?</div><div style=3D"font-size:12.8000001907349px"><br><=
/div><div style=3D"font-size:12.8000001907349px">That is 4 octets for the `=
$` header, and the rest for the the packet header which can then be inspect=
ed to be the same version, payloadtype and ssrc as required by the client.<=
/div><div style=3D"font-size:12.8000001907349px"><br></div><div style=3D"fo=
nt-size:12.8000001907349px">This prevents a client who may also send a &quo=
t;GET_PARAMETER&quot; under interleaved transport with weird headers and a =
body to attempt underflow also which is something the current specification=
 does nothing to protect against.</div><div style=3D"font-size:12.800000190=
7349px"><br></div><div style=3D"font-size:12.8000001907349px">&quot;GET_PAR=
AMATER rtsp://someuri/ RTSP/1.0\r\nCSeq:1\r\nDate: xx:xx:xx\r\nContent-Leng=
th:24\r\n$UserAgent $009\r\n$\0\0\aRTSP/1.$\0\0\r\n\r\nDatawith$IsNotAGoodI=
dea!\0\0&quot;<br></div><div style=3D"font-size:12.8000001907349px"><br></d=
iv><div style=3D"font-size:12.8000001907349px">This would allow application=
s to still take note of when a large frame was seen but not be forced to ac=
t upon it and potentially lose data, and depending on their implementation =
allow remote code execution.</div><div style=3D"font-size:12.8000001907349p=
x"><br></div><div style=3D"font-size:12.8000001907349px">I urge the committ=
ee to seriously look into these issues as they can have a large impact in b=
oth interpretation of the standard and it&#39;s security features.</div><di=
v style=3D"font-size:12.8000001907349px"><br></div><div style=3D"font-size:=
12.8000001907349px"><a href=3D"https://isecpartners.github.io/fuzzing/vulne=
rabilities/2013/12/30/vlc-vulnerability.html" target=3D"_blank">https://ise=
cpartners.github.io/fuzzing/vulnerabilities/2013/12/30/vlc-vulnerability.ht=
ml</a></div></div><div><span style=3D"font-size:12.8000001907349px"><br></s=
pan></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">O=
n Mon, Jan 5, 2015 at 10:52 PM, Dale R. Worley <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:worley@ariadne.com" target=3D"_blank">worley@ariadne.com</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">Julius F=
riedman &lt;<a href=3D"mailto:juliusfriedman@gmail.com">juliusfriedman@gmai=
l.com</a>&gt; writes:<br>
&gt; I would like to address your response:<br>
&gt;<br>
&gt; &quot;In any case, why would we want to prevent seeking on a stored me=
dia<br>
&gt; object?=C2=A0 I can see why if the media is an un-stored media stream,=
 but in<br>
&gt; that case, the software likely doesn&#39;t know the total length that =
the<br>
&gt; media will have.&quot;<br>
&gt;<br>
&gt; I will justify how &quot;likely&quot; this is as follows:<br>
&gt;<br>
&gt; 1) A Live 10 minute `media` which has been playing for 3 minutes, leav=
ing<br>
&gt; me 7 minutes in play but unable to seek.<br>
&gt;=C2=A0 =C2=A0 a) If the stream was stored or recorded this obviously wo=
uldn&#39;t be an<br>
&gt; issue<br>
<br>
</span>But how would we know that the media is 10 minutes long if it was no=
t<br>
already stored?=C2=A0 If it was truly live, we&#39;d only know that it was<=
br>
*scheduled* to be 10 minutes long, not that it will actually *be* 10<br>
minutes long.<br>
<span class=3D""><br>
&gt; 2) I have a server which requires authorization to seek but not to pla=
y.<br>
<br>
</span>Why would we want to support that?<br>
<span class=3D""><br>
&gt; 3) I am a client and I have started playing and &#39;PAUSE&#39; is not=
 supported<br>
&gt;<br>
&gt; 4) I am a server re-streaming from a server where &quot;Range&quot; is=
 not supported<br>
<br>
</span>I&#39;m no expert in RTSP, but my understanding is that these two si=
tuations<br>
are only expected to happen when the media is truly live, that is, the<br>
server does not know how long the media will be.<br>
<span class=3D""><br>
&gt; &quot;Perhaps referring to the mailing list discussion for this RFC wo=
uld<br>
&gt; reveal the answer.&quot;<br>
&gt;<br>
&gt; Which mailing list is that? &#39;mmusic&#39; they have also been addre=
ssed, several<br>
&gt; times. I never get a response from them.<br>
<br>
</span>I assume you mean &quot;I have asked before on mmusic and received n=
o<br>
response.&quot;=C2=A0 Perhaps nobody else cares about the proposed capabili=
ty?<br>
<br>
I mean the mailing list discussion surrounding this document when it was<br=
>
made an RFC.=C2=A0 (Better, look up the Internet-Draft name and refer to th=
e<br>
appropriate mailing list archive for the time when the I-D was being<br>
discussed.)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Dale<br>
</font></span></blockquote></div><br></div>

--047d7bd909a0f9ddc0050bfc7550--


From nobody Tue Jan  6 11:22:43 2015
Return-Path: <worley@alum.mit.edu>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C41E1A1B59 for <avt@ietfa.amsl.com>; Tue,  6 Jan 2015 11:22:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HW-KGV_s99k6 for <avt@ietfa.amsl.com>; Tue,  6 Jan 2015 11:22:20 -0800 (PST)
Received: from resqmta-po-02v.sys.comcast.net (resqmta-po-02v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:161]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3A761A1B57 for <avt@ietf.org>; Tue,  6 Jan 2015 11:22:20 -0800 (PST)
Received: from resomta-po-05v.sys.comcast.net ([96.114.154.229]) by resqmta-po-02v.sys.comcast.net with comcast id cjMp1p0064xDoy801jNK4U; Tue, 06 Jan 2015 19:22:19 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-po-05v.sys.comcast.net with comcast id cjNJ1p00T1KKtkw01jNKHM; Tue, 06 Jan 2015 19:22:19 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id t06JMI7d013700; Tue, 6 Jan 2015 14:22:18 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id t06JMH0w013696; Tue, 6 Jan 2015 14:22:17 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Julius Friedman <juliusfriedman@gmail.com>
In-Reply-To: <CACFvNHUGDyJDKA0vpPQeKN1H4TCU_8VzuP2Y-V22Jx4XuYJW9w@mail.gmail.com> (juliusfriedman@gmail.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 06 Jan 2015 14:22:17 -0500
Message-ID: <87y4pfd89i.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1420572139; bh=+Znmde4+pj9VxNZ00MaMISzCRE/2EVrXpzp9OJRphHg=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=tP34gqkfNLCvXlbkPmxrzMRnszocO754tY1/KhX9SQ8NvcE7EQ/o+nWNEdAVdGMZv bgxMREToi9BAMN6+SNb26gK566z1yJPoy47UPUBTHr5WkdJ7OUMT+BZyGI/RMAeXZi bYidGfqkXZfSbe9QTrl3aIIkhw0xCP9aBLzkH43GGSwm7sqIbD3X17QDZ+3yziwsGr 01nYIaF8C/G1rB+BcdlsObzV3KA5bTjf+DIRDbYuAJ/s7C3ngJwPOqsAzz/i8uamDh urbPV9kRBSaUQ8U1yRdcovIly4bQt3dfF6faEVEFhyOeqDVCvvROK77qEVo2lDmc/m /WW+KuYRWWzQQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/o7624b6a593UXaH8Jx50ONaYCZw
Cc: avt@ietf.org, mmusic@ietf.org
Subject: Re: [AVTCORE] Question
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 19:22:23 -0000

I'll note that I've received this message directly

Julius Friedman <juliusfriedman@gmail.com> writes:
> As for my other 'issues' / errata for RFC2435 has anything been determined
> on them?

Not yet, clearly.  What are you going to do to get them discussed?

> I will include their questions here again and I would appreciate a single
> complete and through reply.

That is the least effective way to get your issues handled.

First, you are *demanding* something, and that always makes people less
interested in helping you.

Second, you want a "single complete and through reply", which means that
if someone doesn't feel like doing all the work to do that, they won't
bother to do any of the work.  That is, it minimizes the chance that
you'll get any response at all.

A better approach would be to select one problem, the one you think
other people are most likely to recognize as a problem, and ask about
it.  Also, add whatever discussion you can provide, to indicate that
you've done as much work on the problem as you can before asking others.

It seems to me this one would be a good one to start with:

> What about my questions regarding the 'source' and 'ssrc' parameters? Those
> aren't proposals, those are genuine questions.

Note that while RFC 2326 talks about a 'source' parameter, it doesn't
provide any BNF for it.  Suggest that it probably has the same BNF as
the 'destination' parameter.  Show that BNF.  Show all the examples of
source parameters that you know of (mention what devices generate them),
compare them to your suggested BNF.  Add your discussion of security
questions.

Once you've solicited as much feedback as you can get, organize all that
information into a well-written errata for the RFC.

Then go on to the next issue.

> As for my other 'issues' / errata for RFC2435 has anything been determined
> on them?

http://www.rfc-editor.org/errata_search.php?rfc=2435&rec_status=15&presentation=table

All of your errata on RFC 2435 have status "reported", so it appears the
answer is "no".

Dale


From nobody Tue Jan  6 11:29:03 2015
Return-Path: <worley@alum.mit.edu>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E14231A1B40 for <avt@ietfa.amsl.com>; Tue,  6 Jan 2015 11:29:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OiLl_9YLfZj6 for <avt@ietfa.amsl.com>; Tue,  6 Jan 2015 11:29:01 -0800 (PST)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A1611A1AA8 for <avt@ietf.org>; Tue,  6 Jan 2015 11:29:00 -0800 (PST)
Received: from resomta-ch2-13v.sys.comcast.net ([69.252.207.109]) by resqmta-ch2-08v.sys.comcast.net with comcast id cjTC1p0082N9P4d01jV0B7; Tue, 06 Jan 2015 19:29:00 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-ch2-13v.sys.comcast.net with comcast id cjUz1p00J1KKtkw01jUzu5; Tue, 06 Jan 2015 19:29:00 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id t06JSxMb014531; Tue, 6 Jan 2015 14:28:59 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id t06JSwef014528; Tue, 6 Jan 2015 14:28:58 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: worley@ariadne.com (Dale R. Worley)
In-Reply-To: <87d26sefaw.fsf@hobgoblin.ariadne.com> (worley@ariadne.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 06 Jan 2015 14:28:58 -0500
Message-ID: <87vbkjd7yd.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1420572540; bh=X0aUnVAA35QxEIE61pty1yRU5kjWye7QT4MLIMIZBuw=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=q6OxRAcSMbwiOJaabhfWiSDqhwDkEguJO7bLqn2wLpgQOyPmWOrFU09auZkbFzePI PWPJrOoaKMqp5asgVGWapIh9wkvh4lYty86kZzDIZjKaEwQz2s4AT5PSy3IrJ83gjN +0n4gFkaWQ9Vr3h1CuoPytLqN/eX02dzL31gukLbbMoCIRiRjr6Qtke8XzeAKSbv7D eMiITMuAiSIUF/wPvbqgTK5IqwpVdXrCYp3cGdO6YTH8bUiX8SZhTpuZRTZ/mzQkXZ rfx7Cmt1KnlIDPv1qezQyDsgoCQ3EJyQy6wF4mzZT4RFvdEWxK1FWpmVsAA5n4rk/V BKR8WiljDaecg==
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/1nYm_VAOLoMs0CceyHNEaYbZSRc
Cc: juliusfriedman@gmail.com, avt@ietf.org, mmusic@ietf.org
Subject: [AVTCORE] Erratum 4097 on RFC 2435
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 19:29:03 -0000

I've looked at this erratum
(http://www.rfc-editor.org/errata_search.php?eid=4097) and I don't think
I understand it.

It contains a section titled "Section 3.1.5 says" and a section titled
"It should say", but the bodies of the two sections are exactly the
same.  (I used a text editor to compare them.)  So what change is
described by the erratum?

There is a section titled "Notes" which says:

    Use a divisor of 256 to determine the height, where 8 / 256 = 32.

    Ensure FragmentOffset does not exceed 2^24, if it does then use 2^24
    - value)

The first line does not seem to describe the computation described in
the RFC text, and the equation in that line is incorrect.  (Was it
supposed to be 256 / 8 = 32?)

The second line seems to be entirely unrelated to the rest of the
erratum.  Perhaps it belongs in another erratum?  It also contains an
unmatched ")".

Dale


From nobody Wed Jan  7 10:27:40 2015
Return-Path: <juliusfriedman@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B52751A0275; Wed,  7 Jan 2015 10:27:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bG8i1SIbWid4; Wed,  7 Jan 2015 10:27:32 -0800 (PST)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D43B11A00E9; Wed,  7 Jan 2015 10:27:31 -0800 (PST)
Received: by mail-pd0-f170.google.com with SMTP id v10so6164979pde.1; Wed, 07 Jan 2015 10:27:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=L1hyVVoTnQgyiZPYik0XUikFpXdWXamI0xi4sktbDdw=; b=Z6rBzVvex3CEFqp8alNQp1lz8XSPPn3dBO6DtTnuAjNNJGQPvWScMrNykXSP26z66G Q8U8n4+QgN9E/2wHxBnYzRU+QFm+EroalV7X5y2R8Tg64z4s/3ilwW7jbUrRCAraXfHW mipAPyzKoxxG33spIoceBZMgDSaPM7v6YYWadtotHBKPZz/CdL8SkxDJA4Yq7cTA0MnD h9QnvHIoEI+z9YtbApGnen4cMif9hAO/7cXSKW8ZjTxn2sisZEu8KxXWtBtWi2Msclzc Xw1McHiBPbAbMjxZhcPP8z0mkXuA+N7cXZcYQXA9G7zkP4YwKaY/qiET5GpAUTpCFdgR +UNg==
MIME-Version: 1.0
X-Received: by 10.68.57.167 with SMTP id j7mr7813075pbq.160.1420655250979; Wed, 07 Jan 2015 10:27:30 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Wed, 7 Jan 2015 10:27:30 -0800 (PST)
In-Reply-To: <D0D17717.4E344%stewe@stewe.org>
References: <CACFvNHUGDyJDKA0vpPQeKN1H4TCU_8VzuP2Y-V22Jx4XuYJW9w@mail.gmail.com> <87y4pfd89i.fsf@hobgoblin.ariadne.com> <D0D17717.4E344%stewe@stewe.org>
Date: Wed, 7 Jan 2015 13:27:30 -0500
Message-ID: <CACFvNHVkDBXfPKaAk1V8N+XRSfLg4-snWWbbLxJb2w7W97ZzJg@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: Stephan Wenger <stewe@stewe.org>, avt@ietf.org, mmusic@ietf.org
Content-Type: multipart/alternative; boundary=001a113805ec95464f050c1413df
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/RPZtuUQJS0hau_9EkFoSdRamnEg
Subject: Re: [AVTCORE] [MMUSIC]  Question
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jan 2015 18:27:36 -0000

--001a113805ec95464f050c1413df
Content-Type: text/plain; charset=UTF-8

@Dave & Stephan,

Well thanks for letting me know at least someone sees these messages.

I am not demanding anything, I had these inquiries for over 6 months and
when I received no response I filled the erratum. If there is a better way
so be it but respond and indicate such. I will retract erratum if I am
wrong or it is determined to not be applicable.

Right now basically when I use the advice I am given, the people that gave
it to me get offended, well how do you think I feel when it was told to me
the same things? e.g. "RTP has worked for 20 years" or "Mr. Casner is the
worlds leading expert" or "Collin Perkins didn't respond" Who cares? That
was not a scope of my issue and more spam then any of my inquires
contained. If they don't want to respond they don't have to, the issues are
still real.

I am open to writing a draft to correct things but there is nothing to
write about if people can't get over the fact that there are issues which I
attempted to openly addressed, weather or not people respond doesn't really
make a difference in the end I guess as I can't really DO anything to FORCE
you to address these issues, I can only file errata and if the errata is
accepted so be it. I have my own software to worry about and that's where
my focus will be, it will be unfortunate if I have to explain why I
explicitly chose not to be 'complaint' but its more so to just pretend like
it was 'intended' and hide behind the details.

That being said I do apologize if I stepped on any toes or hurt anyone's
`ego`, I don't intend to do that and I didn't bring the conversation in
those directions anyway. I just want to address the issues and move on.

Relating to my RFC2435 Errata.

YES, this is correct, I apologize for the backwards calculation.

The RFC only provided a way for certain sized images much lower then what
JPEG supports to be transferred, this erratum fixes this by specifying that
in some cases you may need to use a different fraction to obtain the height
(which might not be in a multiple of 16 anyway) additionally it allows one
to deal with the nuance that if the data is so large that the
FragmentOffset will probably overflow during this time and provides a way
to deal with that as well.

I just wanted to determine if there was any consensus around
my proposed change, do you recommend I add another erratum for the
`FragmentOffset` issue? And yes the 'Unmatched brace' is also my bad.

There are actually two others which can be seen here: (and possibly more
important)

http://www.rfc-editor.org/errata_search.php?rfc=2435&rec_status=15&presentation=records

They related to the types of JPEG which can be transferred under the RFC
and the tables used for quantization when quality is <=
50, specifically there are problems for black and white jpeg's and jpegs
with more then 2 quantization tables. My implementation handles all of this
but the code given in the RFC does not.  You can find my code @
http://net7mma.codeplex.com/SourceControl/latest#RtspServer/MediaTypes/RFC2435Media.cs
or the corrected code in the erratum.

Thank you for your input and I would appreciate taking the next steps on
those if possible so please let me know what to do next if anything.

I see that my 'RTSP' errata (4199) is `reported` and that it contains a
typo as I previously indicated, no one seems to have responded to that, I
can only imagine that it's known but no one really understand or knows what
to do about it and furthermore it seems that in the latest draft there have
been quite a few changes which remedy my questions in some regard but not
totally.

As for the updated RTSP Standard, I will say that the standard does seem
greatly improved as of the latest version @
http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40

I will definitely be using some of the information present to deal with my
issues with 'Live' non-stored streams, such as the 'Media-Properties' and `
Seek-Style` header.

I do have a few questions related to the content however which hopefully
can be resolved before any further issue comes up.


13 <http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#section-13>.
Method Definitions

   The method indicates what is to be performed on the resource
   identified by the Request-URI.  The method name is case-sensitive.
   New methods may be defined in the future.  Method names MUST NOT
   start with a $ character (decimal 36) and MUST be a token as defined
   by the ABNF [RFC5234 <http://tools.ietf.org/html/rfc5234>] in the
syntax chapter Section 20
<http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#section-20>.
The methods
   are summarized in Table 7.

...

Why does it make sense to work around the issue that '$' is both the
framing character and now officially a 'SAFE' character?


Rather than change the framing method to something which would be
better for TCP since it's only used there we simply make it worse by
removing the ambiguity of '\$' and now saying that '$' is safe.


So now we can also have '$' Methods like "METHOD_$" that's not a great
feature... I think that 36 needs to be removed from the header section
all together. It should simply not appear in the header section under
any cases.


CSeq and Date (etc) should use Hex rather than Decimal notation which
would remove most of the issues with it's occurrence. The body section
is not an issue as it's length and encoding is given.



14 <http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#section-14>.
Embedded (Interleaved) Binary Data

Note that this mechanism does not support PDUs larger than 65535
      octets, which matches the maximum payload size of regular, non-
      jumbo IPv4 and IPv6 packets.  If the media delivery protocol
      intended to be used has larger PDUs than that, definition of a PDU
      fragmentation mechanism will be required to support embedded
      binary data.

...


TCP can technically be fragmented or overlapped without such large
packets so what does this statement provide?

The fact my network users larger packets would make no different as I
likely wouldn't be sending those packets outside my network.


How should one specify such as mechanism which is both compatible with
existing interleaving and this new mechanism? Without a better Binary
Interleaved Header it would be almost fruitless anyway since the TCP
protocol does not allow developers to take advantage of the
re-transmissions configuration per socket or disable receive
coalescing. (Although some Linux / Unix implementations do allow this
via TCP_USER_TIMEOUT on Windows these are per Machine or per Adapter
settings).



18.53 <http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#section-18.53>.
Timestamp

   The Timestamp general-header describes when the agent sent the
   request.  The value of the timestamp is of significance only to the
   agent and may use any timescale.  The responding agent MUST echo the
   exact same value and MAY, if it has accurate information about this,
   add a floating point number indicating the number of seconds that has
   elapsed since it has received the request.  The timestamp can be used
   by the agent to compute the round-trip time to the responding agent

   so that it can adjust the timeout value for retransmissions when
   running over an unreliable protocol.  It also resolves retransmission
   ambiguities for unreliable transport of RTSP.

   Note that the present specification provides only for reliable
   transport of RTSP messages.  The Timestamp general-header is
   specified in case the protocol is extended in the future to use
   unreliable transport.

...

I already support Rtsp over UDP, I am not going to disable just
because there was a 'lack of interest', if I am interested or my
clients are we are going to use it.


I think the verbiage here is misleading 'in case the protocol is
extended in the future to use  unreliable transport.'  How can it be
that in the future when it was supported in previous versions?
Furthermore what happened to the nomenclature about disabling
re-tranmissions? Is that no longer required?


Also I don't need this header to compute "Round Trip Time" no does
anyone else NOR should it be used in place of the actual round trip
time as locally calculated, only the delay portion added by the server
is even remotely relevant.


Section 18.54 <http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#section-18.54>.
Transport



...

ssrc: The ssrc parameter, if included in a SETUP response, indicates
         the RTP SSRC [RFC3550 <http://tools.ietf.org/html/rfc3550>]
value(s) that will be used by the media
         server for RTP packets within the stream.  It is expressed as
         an eight digit hexadecimal value.

         The ssrc parameter MUST NOT be specified in requests.  The
         functionality of specifying the ssrc parameter in a SETUP
         request is deprecated as it is incompatible with the
         specification of RTP in RFC 3550
<http://tools.ietf.org/html/rfc3550>[RFC3550
<http://tools.ietf.org/html/rfc3550>].  If the parameter is
         included in the Transport header of a SETUP request, the server
         SHOULD ignore it, and choose appropriate SSRCs for the stream.
         The server SHOULD set the ssrc parameter in the Transport
         header of the response.


Why is this not compatible? It would surely alleviate issues under TCP
where the first RTCP packet was received before the `PLAY` response.


Why should the client not be able to indicate it's 'ssrc' space to the
server to ensure a collision is not occurring?


Wouldn't it also be incompatible for the server to send the `ssrc` so
why is the semantic different for the client?



'RTCP-mux'

Can't a server just use a single client_port or use the same port twice?
e.g. "client_port=1234" OR "client_port=1234-1234"?

Can it at-least be stated that RTCP-mux would be equivalent to the above
syntax (since I do believe that's how it's achieved now anyhow)? If not
what is to be assumed if there is not a pair of ports? that Rtcp is
disabled?

Thank to those that are responding!

--001a113805ec95464f050c1413df
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>@Dave &amp; Stephan,</div><div><br></div><div>Well th=
anks for letting me know at least someone sees these messages.</div><div><b=
r></div><div>I am not demanding anything, I had these inquiries for over 6 =
months and when I received no response I filled the erratum. If there is a =
better way so be it but respond and indicate such. I will retract erratum i=
f I am wrong or it is determined to not be applicable.</div><div><br></div>=
<div>Right now basically when I use the advice I am given, the people that =
gave it to me get offended, well how do you think I feel when it was told t=
o me the same things? e.g. &quot;RTP has worked for 20 years&quot; or &quot=
;Mr. Casner is the worlds leading expert&quot; or &quot;Collin Perkins didn=
&#39;t respond&quot; Who cares? That was not a scope of my issue and more s=
pam then any of my inquires contained. If they don&#39;t want to respond th=
ey don&#39;t have to, the issues are still real.</div><div><br></div><div>I=
 am open to writing a draft to correct things but there is nothing to write=
 about if people can&#39;t get over the fact that there are issues which I =
attempted to openly addressed, weather or not people respond doesn&#39;t re=
ally make a difference in the end I guess as I can&#39;t really DO anything=
 to FORCE you to address these issues, I can only file errata and if the er=
rata is accepted so be it. I have my own software to worry about and that&#=
39;s where my focus will be, it will be unfortunate if I have to explain wh=
y I explicitly chose not to be &#39;complaint&#39; but its more so to just =
pretend like it was &#39;intended&#39; and hide behind the details.</div><d=
iv><br></div><div>That being said I do apologize if I stepped on any toes o=
r hurt anyone&#39;s `ego`, I don&#39;t intend to do that and I didn&#39;t b=
ring the conversation in those directions anyway. I just want to address th=
e issues and move on.</div><div><br></div><div>Relating to my RFC2435 Errat=
a.</div><div><br></div><div><span style=3D"font-size:12.8000001907349px">YE=
S, this is correct, I=C2=A0apologize for the backwards=C2=A0calculation.=C2=
=A0</span></div><div><span style=3D"font-size:12.8000001907349px"><br></spa=
n></div><div><span style=3D"font-size:12.8000001907349px">The RFC only prov=
ided a way for certain sized images much lower then what JPEG supports to b=
e transferred, this erratum fixes this by specifying that in some cases you=
 may need to use a different fraction to obtain the height (which might not=
 be in a multiple of 16 anyway) additionally it allows one to deal with the=
 nuance that if the data is so large that the FragmentOffset will probably=
=C2=A0overflow=C2=A0during this time and provides a way to deal with that a=
s well.</span><br style=3D"font-size:12.8000001907349px"><br style=3D"font-=
size:12.8000001907349px"><span style=3D"font-size:12.8000001907349px">I jus=
t wanted to determine if there was any consensus around my=C2=A0proposed=C2=
=A0change, do you recommend I add another erratum for the `FragmentOffset` =
issue? And yes the &#39;Unmatched brace&#39; is also my bad.</span></div><d=
iv><span style=3D"font-size:12.8000001907349px"><br></span></div><div><span=
 style=3D"font-size:12.8000001907349px">There are actually two others which=
 can be seen here: (and possibly more important)</span></div><div><span sty=
le=3D"font-size:12.8000001907349px"><br></span></div><div><span style=3D"fo=
nt-size:12.8000001907349px"><a href=3D"http://www.rfc-editor.org/errata_sea=
rch.php?rfc=3D2435&amp;rec_status=3D15&amp;presentation=3Drecords">http://w=
ww.rfc-editor.org/errata_search.php?rfc=3D2435&amp;rec_status=3D15&amp;pres=
entation=3Drecords</a></span><br></div><div><span style=3D"font-size:12.800=
0001907349px"><br></span></div><div><span style=3D"font-size:12.80000019073=
49px">They related to the types of JPEG which can be=C2=A0transferred=C2=A0=
under the RFC and the tables used for quantization when quality is &lt;=3D =
50,=C2=A0specifically=C2=A0there are problems for black and white jpeg&#39;=
s and jpegs with more then 2 quantization tables. My=C2=A0implementation=C2=
=A0handles all of this but the code given in the RFC does not.=C2=A0 You ca=
n find my code @=C2=A0<a href=3D"http://net7mma.codeplex.com/SourceControl/=
latest#RtspServer/MediaTypes/RFC2435Media.cs">http://net7mma.codeplex.com/S=
ourceControl/latest#RtspServer/MediaTypes/RFC2435Media.cs</a> or the correc=
ted code in the erratum.</span></div><div><span style=3D"font-size:12.80000=
01907349px"><br></span></div><div><span style=3D"font-size:12.8000001907349=
px">Thank you for your input and I would appreciate taking the next steps o=
n those if possible so please let me know what to do next if anything.</spa=
n></div><div><span style=3D"font-size:12.8000001907349px"><br></span></div>=
<div><span style=3D"font-size:12.8000001907349px">I see that my &#39;RTSP&#=
39; errata (4199) is `reported` and that it contains a typo as I previously=
 indicated, no one seems to have=C2=A0responded=C2=A0to that, I can only im=
agine that it&#39;s known but no one really understand or knows what to do =
about it</span><span style=3D"font-size:12.8000001907349px">=C2=A0and furth=
ermore it seems that in the latest draft there have been quite a few change=
s which remedy my questions in some=C2=A0regard</span><span style=3D"font-s=
ize:12.8000001907349px">=C2=A0but not totally.</span></div><div><span style=
=3D"font-size:12.8000001907349px"><br></span></div><div><span style=3D"font=
-size:12.8000001907349px">As for the updated RTSP Standard,=C2=A0</span>I w=
ill say that the standard does seem greatly improved as of the latest versi=
on @=C2=A0<a href=3D"http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bi=
s-40" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-mmusic-rfc232=
6bis-40</a></div><div><br></div><div>I will definitely be using some of the=
 information present to deal with my issues with &#39;Live&#39; non-stored =
streams, such as the &#39;Media-Properties&#39; and `<span style=3D"color:r=
gb(0,0,0);font-size:1em">Seek-Style`=C2=A0</span>header.</div><div><br></di=
v><div>I do have a few questions related to the content however which hopef=
ully can be resolved before any further issue comes up.</div><div><pre clas=
s=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,=
0,0)"><span class=3D"" style=3D"line-height:0pt;display:inline;font-size:1e=
m;font-weight:bold"><br></span></pre><pre class=3D"" style=3D"font-size:1em=
;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span class=3D"" style=
=3D"line-height:0pt;display:inline;font-size:1em;font-weight:bold"><h2 styl=
e=3D"line-height:0pt;display:inline;font-size:1em"><a class=3D"" name=3D"se=
ction-13" href=3D"http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-4=
0#section-13" style=3D"color:black;text-decoration:none">13</a>.  Method De=
finitions</h2></span>

   The method indicates what is to be performed on the resource
   identified by the Request-URI.  The method name is case-sensitive.
   New methods may be defined in the future.  Method names MUST NOT
   start with a $ character (decimal 36) and MUST be a token as defined
   by the ABNF [<a href=3D"http://tools.ietf.org/html/rfc5234" title=3D"&qu=
ot;Augmented BNF for Syntax Specifications: ABNF&quot;">RFC5234</a>] in the=
 syntax chapter <a href=3D"http://tools.ietf.org/html/draft-ietf-mmusic-rfc=
2326bis-40#section-20">Section 20</a>.  The methods
   are summarized in Table 7.</pre><pre class=3D"" style=3D"font-size:1em;m=
argin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span style=3D"color:rgb(=
34,34,34);font-family:arial,sans-serif;font-size:small;white-space:normal">=
...</span><br></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0=
px"><font face=3D"arial, sans-serif"><span style=3D"white-space:normal">Why=
 does it make sense to work around the issue that &#39;$&#39; is both the f=
raming character and now=C2=A0officially=C2=A0a &#39;SAFE&#39; character?</=
span></font></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px=
"><font face=3D"arial, sans-serif"><span style=3D"white-space:normal"><br><=
/span></font></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0p=
x"><font face=3D"arial, sans-serif"><span style=3D"white-space:normal">Rath=
er than change the framing method to something which would be better for TC=
P since it&#39;s only used there we simply make it worse by removing the am=
biguity of &#39;\$&#39; and now saying that &#39;$&#39; is safe.</span></fo=
nt></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font f=
ace=3D"arial, sans-serif"><span style=3D"white-space:normal"><br></span></f=
ont></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font =
face=3D"arial, sans-serif"><span style=3D"white-space:normal">So now we can=
 also have &#39;$&#39; Methods like &quot;METHOD_$&quot; that&#39;s not a g=
reat feature... I think that 36 needs to be removed from the header section=
 all together. It should simply not appear in the header section under any =
cases.</span></font></pre><pre class=3D"" style=3D"margin-top:0px;margin-bo=
ttom:0px"><font face=3D"arial, sans-serif"><span style=3D"white-space:norma=
l"><br></span></font></pre><pre class=3D"" style=3D"margin-top:0px;margin-b=
ottom:0px"><font face=3D"arial, sans-serif"><span style=3D"white-space:norm=
al">CSeq and Date (etc) should use Hex rather than Decimal notation which w=
ould remove most of the issues with it&#39;s=C2=A0occurrence. The body sect=
ion is not an issue as it&#39;s length and encoding is given.</span></font>=
</pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=
=3D"arial, sans-serif"><span style=3D"white-space:normal"><br></span></font=
></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font fac=
e=3D"arial, sans-serif"><span style=3D"white-space:normal"><br></span></fon=
t></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><pre cla=
ss=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0=
,0,0)"><span class=3D"" style=3D"line-height:0pt;display:inline;font-size:1=
em;font-weight:bold"><h2 style=3D"line-height:0pt;display:inline;font-size:=
1em"><a class=3D"" name=3D"section-14" href=3D"http://tools.ietf.org/html/d=
raft-ietf-mmusic-rfc2326bis-40#section-14" style=3D"color:black;text-decora=
tion:none">14</a>.  Embedded (Interleaved) Binary Data</h2></span></pre><pr=
e class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:=
rgb(0,0,0)"><span class=3D"" style=3D"line-height:0pt;display:inline;font-s=
ize:1em;font-weight:bold"><h2 style=3D"line-height:0pt;display:inline;font-=
size:1em"><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bott=
om:0px;font-weight:normal;line-height:normal">Note that this mechanism does=
 not support PDUs larger than 65535
      octets, which matches the maximum payload size of regular, non-
      jumbo IPv4 and IPv6 packets.  If the media delivery protocol
      intended to be used has larger PDUs than that, definition of a PDU
      fragmentation mechanism will be required to support embedded
      binary data.</pre></h2></span></pre></pre></div><div><pre class=3D"" =
style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><=
span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm=
all;white-space:normal">...</span><br></pre><pre class=3D"" style=3D"margin=
-top:0px;margin-bottom:0px"><font face=3D"arial, sans-serif"><span style=3D=
"white-space:normal"><br></span></font></pre><pre class=3D"" style=3D"margi=
n-top:0px;margin-bottom:0px"><font face=3D"arial, sans-serif"><span style=
=3D"white-space:normal">TCP can technically be fragmented or overlapped wit=
hout such large packets so what does this statement provide?</span></font><=
/pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=
=3D"arial, sans-serif"><span style=3D"white-space:normal">The fact my netwo=
rk users larger packets would make no different as I likely wouldn&#39;t be=
 sending those packets outside my network.</span></font></pre><pre class=3D=
"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial, sans-ser=
if"><span style=3D"white-space:normal"><br></span></font></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial, sans-=
serif"><span style=3D"white-space:normal">How should one specify such as me=
chanism which is both compatible with existing interleaving and this new=C2=
=A0mechanism? Without a better Binary Interleaved Header it would be almost=
 fruitless anyway since the TCP protocol does not allow developers to take =
advantage of the re-transmissions configuration per socket or disable recei=
ve=C2=A0coalescing. (Although some Linux / Unix implementations do allow th=
is via TCP_USER_TIMEOUT on Windows these are per Machine or per Adapter set=
tings).=C2=A0</span></font></pre><pre class=3D"" style=3D"margin-top:0px;ma=
rgin-bottom:0px"><font face=3D"arial, sans-serif"><span style=3D"white-spac=
e:normal"><br></span></font></pre><pre class=3D"" style=3D"margin-top:0px;m=
argin-bottom:0px"><font face=3D"arial, sans-serif"><span style=3D"white-spa=
ce:normal"><br></span></font></pre><pre class=3D"" style=3D"margin-top:0px;=
margin-bottom:0px"><pre class=3D"" style=3D"font-size:1em;margin-top:0px;ma=
rgin-bottom:0px;color:rgb(0,0,0)"><span class=3D"" style=3D"line-height:0pt=
;display:inline;font-size:1em;font-weight:bold"><h3 style=3D"line-height:0p=
t;display:inline;font-size:1em"><a class=3D"" name=3D"section-18.53" href=
=3D"http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#section-18.5=
3" style=3D"color:black;text-decoration:none">18.53</a>.  Timestamp</h3></s=
pan>

   The Timestamp general-header describes when the agent sent the
   request.  The value of the timestamp is of significance only to the
   agent and may use any timescale.  The responding agent MUST echo the
   exact same value and MAY, if it has accurate information about this,
   add a floating point number indicating the number of seconds that has
   elapsed since it has received the request.  The timestamp can be used
   by the agent to compute the round-trip time to the responding agent</pre=
><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;co=
lor:rgb(0,0,0)">   so that it can adjust the timeout value for retransmissi=
ons when
   running over an unreliable protocol.  It also resolves retransmission
   ambiguities for unreliable transport of RTSP.

   Note that the present specification provides only for reliable
   transport of RTSP messages.  The Timestamp general-header is
   specified in case the protocol is extended in the future to use
   unreliable transport.</pre><pre class=3D"" style=3D"font-size:1em;margin=
-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span style=3D"color:rgb(34,34=
,34);font-family:arial,sans-serif;font-size:small;white-space:normal">...</=
span><br></pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin=
-bottom:0px;color:rgb(0,0,0)"><span style=3D"color:rgb(34,34,34);font-famil=
y:arial,sans-serif;font-size:small;white-space:normal">I already support Rt=
sp over UDP, I am not going to disable just because there was a &#39;lack o=
f interest&#39;, if I am interested or my clients are we are going to use i=
t.</span></pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin=
-bottom:0px;color:rgb(0,0,0)"><span style=3D"color:rgb(34,34,34);font-famil=
y:arial,sans-serif;font-size:small;white-space:normal"><br></span></pre><pr=
e class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial=
, sans-serif"><span style=3D"white-space:normal">I think the=C2=A0verbiage=
=C2=A0here is misleading &#39;</span></font><span style=3D"color:rgb(0,0,0)=
;font-size:1em;font-family:arial,sans-serif">in case the protocol is extend=
ed in the future to use</span><span style=3D"color:rgb(0,0,0);font-size:1em=
;font-family:arial,sans-serif">  unreliable transport.&#39;  </span><span s=
tyle=3D"font-family:arial,sans-serif;white-space:normal">How can it be that=
 in the future when it was supported in previous versions? Furthermore what=
 happened to the nomenclature about disabling re-tranmissions? Is that no l=
onger required?</span></pre><pre class=3D"" style=3D"margin-top:0px;margin-=
bottom:0px"><span style=3D"font-family:arial,sans-serif;white-space:normal"=
><br></span></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px=
"><font face=3D"arial, sans-serif"><span style=3D"white-space:normal">Also =
I don&#39;t need this header to compute &quot;Round Trip Time&quot; no does=
 anyone else NOR should it be used in place of the actual round trip time a=
s locally=C2=A0calculated, only the delay portion added by the server is ev=
en remotely=C2=A0relevant.</span></font></pre></pre></div><div><pre class=
=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0=
,0)"><br></pre></div><div><pre class=3D"" style=3D"font-size:1em;margin-top=
:0px;margin-bottom:0px;color:rgb(0,0,0)"><span class=3D"" style=3D"line-hei=
ght:0pt;display:inline;font-size:1em;font-weight:bold"><h3 style=3D"line-he=
ight:0pt;display:inline;font-size:1em">Section <a class=3D"" name=3D"sectio=
n-18.54" href=3D"http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40=
#section-18.54" style=3D"color:black;text-decoration:none">18.54</a>.  Tran=
sport</h3></span></pre><pre class=3D"" style=3D"font-size:1em;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)"><span class=3D"" style=3D"line-height=
:0pt;display:inline;font-size:1em;font-weight:bold"><h3 style=3D"line-heigh=
t:0pt;display:inline;font-size:1em"><br></h3></span></pre><pre class=3D"" s=
tyle=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><s=
pan class=3D"" style=3D"line-height:0pt;display:inline;font-size:1em;font-w=
eight:bold"><h3 style=3D"line-height:0pt;display:inline;font-size:1em"><br>=
</h3></span></pre></div><div><div>...</div></div><div><pre class=3D"" style=
=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">ssrc: =
The ssrc parameter, if included in a SETUP response, indicates
         the RTP SSRC [<a href=3D"http://tools.ietf.org/html/rfc3550" title=
=3D"&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC35=
50</a>] value(s) that will be used by the media
         server for RTP packets within the stream.  It is expressed as
         an eight digit hexadecimal value.

         The ssrc parameter MUST NOT be specified in requests.  The
         functionality of specifying the ssrc parameter in a SETUP
         request is deprecated as it is incompatible with the
         specification of RTP in <a href=3D"http://tools.ietf.org/html/rfc3=
550">RFC 3550</a>[<a href=3D"http://tools.ietf.org/html/rfc3550" title=3D"&=
quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a=
>].  If the parameter is
         included in the Transport header of a SETUP request, the server
         SHOULD ignore it, and choose appropriate SSRCs for the stream.
         The server SHOULD set the ssrc parameter in the Transport
         header of the response.</pre><pre class=3D"" style=3D"font-size:1e=
m;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre class=
=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0=
,0)"><span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-s=
ize:small;white-space:normal">Why is this not compatible? It would surely a=
lleviate issues under TCP where the first RTCP packet was received before t=
he `PLAY` response.</span><br></pre><pre class=3D"" style=3D"margin-top:0px=
;margin-bottom:0px"><font face=3D"arial, sans-serif"><span style=3D"white-s=
pace:normal"><br></span></font></pre><pre class=3D"" style=3D"margin-top:0p=
x;margin-bottom:0px"><font face=3D"arial, sans-serif"><span style=3D"white-=
space:normal">Why should the client not be able to indicate it&#39;s &#39;s=
src&#39; space to the server to ensure a collision is not=C2=A0occurring?</=
span></font></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px=
"><font face=3D"arial, sans-serif"><span style=3D"white-space:normal"><br><=
/span></font></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0p=
x"><font face=3D"arial, sans-serif"><span style=3D"white-space:normal">Woul=
dn&#39;t it also be incompatible for the server to send the `ssrc` so why i=
s the semantic different for the client?<br></span></font></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial, sans-=
serif"><span style=3D"white-space:normal"><br></span></font></pre></div><di=
v><br></div><div><div>&#39;RTCP-mux&#39;</div><div><br></div><div>Can&#39;t=
 a server just use a single client_port or use the same port twice? e.g. &q=
uot;client_port=3D1234&quot; OR &quot;client_port=3D1234-1234&quot;?</div><=
div><br></div><div>Can it at-least be stated that RTCP-mux would be equival=
ent to the above syntax (since I do believe that&#39;s how it&#39;s achieve=
d now anyhow)? If not what is to be assumed if there is not a pair of ports=
? that Rtcp is disabled?</div></div><div><br></div><div>Thank to those that=
 are responding!</div></div>

--001a113805ec95464f050c1413df--


From nobody Thu Jan  8 10:36:50 2015
Return-Path: <juliusfriedman@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B40651A006C; Thu,  8 Jan 2015 10:36:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.301
X-Spam-Level: 
X-Spam-Status: No, score=0.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MANGLED_LOAN=2.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ihnLS_-dnpyc; Thu,  8 Jan 2015 10:36:43 -0800 (PST)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D48C31A0039; Thu,  8 Jan 2015 10:36:42 -0800 (PST)
Received: by mail-pd0-f182.google.com with SMTP id p10so12629804pdj.13; Thu, 08 Jan 2015 10:36:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=+AnNrztbGDYi0WqSJrIoZYAtO3lO8jtuMu0skpqLttQ=; b=O0V+t2xBdDtj898itmpu2smnmHUi5cxhVdvJdf3FV6BH5QEtrdFMcyIrqDJRHONusF uNhix6kge2AgSvmHI+9iVvqwFaAoZvGl+2G/Gt9ufQRxs4NyFJ6zeLCdIeUaagpVBjLs jp6VYP0ozK4AFFpw56SSz6Mzn7zYyZ2RlQ6AtxukJjxDZPz0d6QaMH56kSh9MJRuBojM j4GUbrO4C86M9P8jdxf1pz/4lt5I5rvIQNjqo7JZqHo15CTuFGxlxaFiNw/WFywQLRgG jjNCaBJhZ/jA+j81ZorItfjXcT5kS7B028uXliSkJAzZM0yehLLtaO0mjTqQy+FszPrb 2FVg==
MIME-Version: 1.0
X-Received: by 10.70.140.130 with SMTP id rg2mr17199384pdb.49.1420742202045; Thu, 08 Jan 2015 10:36:42 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Thu, 8 Jan 2015 10:36:42 -0800 (PST)
Date: Thu, 8 Jan 2015 13:36:42 -0500
Message-ID: <CACFvNHUfQyY9OrAx7iCCR5XLQM7LHKS28WfcJG=FsmWfJ8_BvA@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: avt@ietf.org, mmusic@ietf.org
Content-Type: multipart/alternative; boundary=001a1134c7c8455ccf050c2852a8
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/RRuHpq4Yh7f73QwLTO3Agf_gMSw>
Subject: [AVTCORE] On RFC2326-biz
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jan 2015 18:36:45 -0000

--001a1134c7c8455ccf050c2852a8
Content-Type: text/plain; charset=UTF-8

Reading further into the new draft I had some more feedback and questions
which I feel should be addressed.

I see that the re-transmission text has been moved elsewhere and that
various nomenclature regarding 're-transmission' has been either removed or
it's location and context has changed to totally oppose the previous
concepts put forth... It seems that re-transmission is now only acceptable
under UDP which the standard goes to remove support for?

What about TCP? How should a RTSP 2 system deal with legacy RTSP 1
connection with that regard? I think there are several other places this
mistake was made also.


Appendix G <http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#appendix-G>.
Requirements for Unreliable Transport of RTSP

   This appendix provides guidance for those who want to implement RTSP
   messages over unreliable transports as has been defined in RTSP 1.0
   [RFC2326 <http://tools.ietf.org/html/rfc2326>].  RFC 2326
<http://tools.ietf.org/html/rfc2326> defined the "rtspu" URI scheme
and provided some
   basic information for the transport of RTSP messages over UDP.  The
   information is being provided here as there has been at at least one
   commercial implementation and compatibility with that should be
   maintained.

   The following points should be considered for an interoperable
   implementation:

   o  Requests shall be acknowledged by the receiver.  If there is no
      acknowledgement, the sender may resend the same message after a
      timeout of one round-trip time (RTT).  Any retransmissions due to
      lack of acknowledgement must carry the same sequence number as the
      original request.

   o  The round-trip time can be estimated as in TCP (RFC 6298
<http://tools.ietf.org/html/rfc6298>)
      [RFC6298 <http://tools.ietf.org/html/rfc6298>], with an initial
round-trip value of 500 ms.  An
      implementation may cache the last RTT measurement as the initial
      value for future connections.

   o  The Timestamp header (Section 18.53
<http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#section-18.53>)
is used to avoid the
      retransmission ambiguity problem [Stevens98
<http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#ref-Stevens98>].

   o  The registered default port for RTSP over UDP for the server is
      554.

   o  RTSP messages can be carried over any lower-layer transport
      protocol that is 8-bit clean.

   o  RTSP messages are vulnerable to bit errors and should not be
      subjected to them.

   o  Source authentication, or at least validation that RTSP messages
      comes from the same entity becomes extremely important, as session
      hijacking may be substantially easier for RTSP message transport
      using an unreliable protocol like UDP than for TCP.


Bullet 5 - *TCP is too, what does this statement add?*


*This information in the header seems to contradict what information
is given later on in Appendix I.*


*Additionally the information related to re-transmission and Timestamp
is still ambiguous IMHO as the Timestamp header plays no role TCP
re-transmissions, furthermore since it's syntax [The Timestamp header]
only has meaning to a Client the Server has no way of measuring or
comparing the previous Timestamp unless they attempt parsing of
various ways of conveying the information. *


*There needs to be more definite syntax related to Timestamp and it
needs to further be indicated that TCP re-transmissions can cause
partial data to appear to a receiver and that when using TCP and how
to handle this as I previously indicated. *


*Some text about minimum packet size with respect to Blocksize
utilized would also be beneficial so there is no reason for clients to
attempt to verify data which cannot be verified by a packet with no
Timestamp header (Rtsp or Rtp or otherwise e.g. a Rtcp packet)*


*The contradicting text from Appendix I is listed below.*


"

 *  The description on how rtspu works is not part of the core
         specification and will require external description.  Only that

         it exists is defined here and some requirements for the
         transport is provided.

"


*Additionally this section seems to further contradict the above paragraphs.*


4.2 <http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#section-4.2>.
RTSP IRI and URI

   RTSP 2.0 defines and registers or updates three URI schemes "rtsp",
   "rtsps" and "rtspu".  The usage of the last, "rtspu", is unspecified
   in RTSP 2.0, and is defined here to register the URI scheme that was
   defined in RTSP 1.0.  The "rtspu" scheme indicates unspecified
   transport of the RTSP messages over unreliable transport (UDP in RTSP
   1.0).  An RTSP server MUST respond with an error code indicating the
   "rtspu" scheme is not implemented (501) to a request that carries a
   "rtspu" URI scheme.


Lastly wouldn't that also mean that a client can still use UDP but their
requests simply can't have a 'rtspu' scheme? I am not sure if that wan
intended or not but it seems silly to indicate that the scheme of the
location means anything when in fact the protocol of the connection is what
really matters. Why would anyone care if a client used a different scheme
in their request?

Sincerely,
Julius Friedman

--001a1134c7c8455ccf050c2852a8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Reading further into the new draft I had some more feedbac=
k and questions which I feel should be addressed.<div><br></div><div>I see =
that the re-transmission text has been moved elsewhere and that various nom=
enclature regarding &#39;re-transmission&#39; has been either removed or it=
&#39;s location and context has changed to totally oppose the previous conc=
epts put forth... It seems that re-transmission is now only acceptable unde=
r UDP which the standard goes to remove support for?</div><div><br></div><d=
iv>What about TCP? How should a RTSP 2 system deal with legacy RTSP 1 conne=
ction with that regard? I think there are several other places this mistake=
 was made also.</div><div><br></div><div><div><br><div><pre class=3D"" styl=
e=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span=
 class=3D"" style=3D"line-height:0pt;display:inline;font-size:1em;font-weig=
ht:bold"><h2 style=3D"line-height:0pt;display:inline;font-size:1em"><a clas=
s=3D"" name=3D"appendix-G" href=3D"http://tools.ietf.org/html/draft-ietf-mm=
usic-rfc2326bis-40#appendix-G" style=3D"color:black;text-decoration:none">A=
ppendix G</a>.  Requirements for Unreliable Transport of RTSP</h2></span>

   This appendix provides guidance for those who want to implement RTSP
   messages over unreliable transports as has been defined in RTSP 1.0
   [<a href=3D"http://tools.ietf.org/html/rfc2326" title=3D"&quot;Real Time=
 Streaming Protocol (RTSP)&quot;">RFC2326</a>].  <a href=3D"http://tools.ie=
tf.org/html/rfc2326">RFC 2326</a> defined the &quot;rtspu&quot; URI scheme =
and provided some
   basic information for the transport of RTSP messages over UDP.  The
   information is being provided here as there has been at at least one
   commercial implementation and compatibility with that should be
   maintained.

   The following points should be considered for an interoperable
   implementation:

   o  Requests shall be acknowledged by the receiver.  If there is no
      acknowledgement, the sender may resend the same message after a
      timeout of one round-trip time (RTT).  Any retransmissions due to
      lack of acknowledgement must carry the same sequence number as the
      original request.

   o  The round-trip time can be estimated as in TCP (<a href=3D"http://too=
ls.ietf.org/html/rfc6298">RFC 6298</a>)
      [<a href=3D"http://tools.ietf.org/html/rfc6298" title=3D"&quot;Comput=
ing TCP&#39;s Retransmission Timer&quot;">RFC6298</a>], with an initial rou=
nd-trip value of 500 ms.  An
      implementation may cache the last RTT measurement as the initial
      value for future connections.

   o  The Timestamp header (<a href=3D"http://tools.ietf.org/html/draft-iet=
f-mmusic-rfc2326bis-40#section-18.53">Section 18.53</a>) is used to avoid t=
he
      retransmission ambiguity problem [<a href=3D"http://tools.ietf.org/ht=
ml/draft-ietf-mmusic-rfc2326bis-40#ref-Stevens98">Stevens98</a>].
</pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0=
px;color:rgb(0,0,0)">   o  The registered default port for RTSP over UDP fo=
r the server is
      554.

   o  RTSP messages can be carried over any lower-layer transport
      protocol that is 8-bit clean.

   o  RTSP messages are vulnerable to bit errors and should not be
      subjected to them.

   o  Source authentication, or at least validation that RTSP messages
      comes from the same entity becomes extremely important, as session
      hijacking may be substantially easier for RTSP message transport
      using an unreliable protocol like UDP than for TCP.
</pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0=
px;color:rgb(0,0,0)"><br></pre><pre class=3D"" style=3D"font-size:1em;margi=
n-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><pre class=3D"" style=3D"font=
-size:1em;margin-top:0px;margin-bottom:0px">Bullet 5 - <b>TCP is too, what =
does this statement add?</b></pre></pre><pre class=3D"" style=3D"font-size:=
1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre class=
=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0=
,0)"><b>This information in the header seems to contradict what information=
 is given later on in Appendix I.</b></pre><pre class=3D"" style=3D"font-si=
ze:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><b><br></b></pre>=
<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><b><font color=
=3D"#000000"><span style=3D"font-size:1em">Additionally the information rel=
ated to re-transmission and Timestamp is still </span><span style=3D"font-s=
ize:10.5625px">ambiguous IMHO as the Timestamp header plays no role TCP re-=
transmissions</span>, furthermore since it&#39;s syntax [The Timestamp head=
er] only has meaning to a Client the Server has no way of measuring or comp=
aring the previous Timestamp unless they attempt parsing of various ways of=
 conveying the information. </font></b></pre><pre class=3D"" style=3D"margi=
n-top:0px;margin-bottom:0px"><b><font color=3D"#000000"><br></font></b></pr=
e><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><b><font color=
=3D"#000000">There needs to be more definite syntax related to Timestamp an=
d it needs to further be indicated that TCP re-transmissions can cause part=
ial data to appear to a receiver and that when using TCP and how to handle =
this as I previously indicated.=C2=A0</font></b></pre><pre class=3D"" style=
=3D"margin-top:0px;margin-bottom:0px"><b><font color=3D"#000000"><br></font=
></b></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><b><f=
ont color=3D"#000000">Some text about minimum packet size with respect to B=
locksize utilized would also be beneficial so there is no reason for client=
s to attempt to verify data which cannot be verified by a packet with no Ti=
mestamp header (Rtsp or Rtp or otherwise e.g. a Rtcp packet)</font></b></pr=
e><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><b><font color=
=3D"#000000"><br></font></b></pre><pre class=3D"" style=3D"margin-top:0px;m=
argin-bottom:0px"><b><font color=3D"#000000">The contradicting text from Ap=
pendix I is listed below.</font></b></pre><pre class=3D"" style=3D"font-siz=
e:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><b><br></b></pre><=
pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;colo=
r:rgb(0,0,0)">&quot;</pre><pre class=3D"" style=3D"font-size:1em;margin-top=
:0px;margin-bottom:0px;color:rgb(0,0,0)"><pre class=3D"" style=3D"font-size=
:1em;margin-top:0px;margin-bottom:0px"> *  The description on how rtspu wor=
ks is not part of the core
         specification and will require external description.  Only that</p=
re><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px"=
>         it exists is defined here and some requirements for the
         transport is provided.</pre></pre><pre class=3D"" style=3D"font-si=
ze:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">&quot;</pre><pre =
class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rg=
b(0,0,0)"><br></pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;m=
argin-bottom:0px;color:rgb(0,0,0)"><b>Additionally this section seems to fu=
rther contradict the above paragraphs.</b></pre><pre class=3D"" style=3D"fo=
nt-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><p=
re class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color=
:rgb(0,0,0)"><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-b=
ottom:0px"><span class=3D"" style=3D"line-height:0pt;display:inline;font-si=
ze:1em;font-weight:bold"><h3 style=3D"line-height:0pt;display:inline;font-s=
ize:1em"><a class=3D"" name=3D"section-4.2" href=3D"http://tools.ietf.org/h=
tml/draft-ietf-mmusic-rfc2326bis-40#section-4.2" style=3D"color:black;text-=
decoration:none">4.2</a>.  RTSP IRI and URI</h3></span>

   RTSP 2.0 defines and registers or updates three URI schemes &quot;rtsp&q=
uot;,
   &quot;rtsps&quot; and &quot;rtspu&quot;.  The usage of the last, &quot;r=
tspu&quot;, is unspecified
   in RTSP 2.0, and is defined here to register the URI scheme that was
   defined in RTSP 1.0.  The &quot;rtspu&quot; scheme indicates unspecified
   transport of the RTSP messages over unreliable transport (UDP in RTSP
   1.0).  An RTSP server MUST respond with an error code indicating the
   &quot;rtspu&quot; scheme is not implemented (501) to a request that carr=
ies a
   &quot;rtspu&quot; URI scheme.</pre></pre></div><div><br></div></div><div=
>Lastly wouldn&#39;t that also mean that a client can still use UDP but the=
ir requests simply can&#39;t have a &#39;rtspu&#39; scheme? I am not sure i=
f that wan intended or not but it seems silly to indicate that the scheme o=
f the location means anything when in fact the protocol of the connection i=
s what really matters. Why would anyone care if a client used a different s=
cheme in their request?</div><div><br></div><div>Sincerely,</div><div>Juliu=
s Friedman</div></div></div>

--001a1134c7c8455ccf050c2852a8--


From nobody Fri Jan  9 00:47:04 2015
Return-Path: <juliusfriedman@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77C1D1A86E8; Fri,  9 Jan 2015 00:47:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BznhRQvnLWq0; Fri,  9 Jan 2015 00:46:59 -0800 (PST)
Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B02391A701C; Fri,  9 Jan 2015 00:46:59 -0800 (PST)
Received: by mail-pa0-f49.google.com with SMTP id eu11so17237638pac.8; Fri, 09 Jan 2015 00:46:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=byX46TpXrPBGpmnd/HPvVJi5ytQxMSKEo5w4l6rlg4E=; b=eB1rXUWr3OA41bc7mAZXApMwkfQyOui8fsGaGr3ILtcSfAzoz+ZQTeSCs/K24IRQ4L MlQzf+PCzuzu4kC9bCVkavsr+B1i0zHjd3U/mZ1lZ6RSGTZHSWgjhLm/YC490Uu+hhTk Syu6kwzdhuc52txRdKWoFOtAntMCQ7MoOityKDK8z6RUTdl25NinkjZ0xBkoohI7iLmJ 8pYNIGxGVFp6KnDGk8wC14wiTCdxrEarba9Rt4S9/Fypur9vSgH5Ikwg8EkTd5jx+anE xydHMTjmG2xc4VjbTd9gQ6E0T1Vuasfp9d45JNoROrq82h2q+N9c1W0NGo5Wc61RzqEi N+EQ==
MIME-Version: 1.0
X-Received: by 10.68.226.166 with SMTP id rt6mr21825053pbc.120.1420793218851;  Fri, 09 Jan 2015 00:46:58 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Fri, 9 Jan 2015 00:46:58 -0800 (PST)
Date: Fri, 9 Jan 2015 03:46:58 -0500
Message-ID: <CACFvNHXwTm5k7Wiw65A=eSBEF9RqP4FJnNysziFik7vpnqrR4A@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: mmusic@ietf.org, avt@ietf.org
Content-Type: multipart/alternative; boundary=e89a8ff246ed1bee84050c3433b2
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/4wlWiklNAKRKCYI_jI5xABQMYJw>
Subject: [AVTCORE] New Possible Errata in RFC2326 (And Draft) regarding Blocksize
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jan 2015 08:47:02 -0000

--e89a8ff246ed1bee84050c3433b2
Content-Type: text/plain; charset=UTF-8

Please see the following two paragraphs regarding Blocksize.

12.7 Blocksize

   This request header field is sent from the client to the media server
   asking the server for a particular media packet size. This packet
   size does not include lower-layer headers such as IP, UDP, or RTP.
   The server is free to use a blocksize which is lower than the one
   requested. The server MAY truncate this packet size to the closest
   multiple of the minimum, media-specific block size, or override it
   with the media-specific size if necessary. The block size MUST be a
   positive decimal number, measured in octets. The server only returns
   an error (416) if the value is syntactically invalid.


18.10 <http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#section-18.10>.
Blocksize

   The Blocksize request-header field is sent from the client to the
   media server asking the server for a particular media packet size.
   This packet size does not include lower-layer headers such as IP,

   UDP, or RTP.  The server is free to use a blocksize which is lower
   than the one requested.  The server MAY truncate this packet size to
   the closest multiple of the minimum, media-specific block size, or
   override it with the media-specific size if necessary.  The block
   size MUST be a positive decimal number, measured in octets.  The
   server only returns an error (4xx) if the value is syntactically
   invalid.


Both paragraphs go to specify that the number MUST be positive but
specify no LOWER bound.


A Blocksize of 12 or less will cause data loss under UDP and cause
invalid framing under TCP.


A Blocksize of >= 12 <= 20 will cause no payload data to be able to be
sent in most profiles which utilize a 4 - 16 byte header.


Therefore the minimum Blocksize must be 21 when RTP is in use and such
a low number of octets in the payload (1) would cause unnecessary
stain on the server.


It should be noted that the Blocksize MUST be a positive decimal
number greater than or equal to that supported by the underlying
transport.


This will prevent a client from undermining the MTU and attempting to
force a server to fragment packets against protocol rules OR perform
re-packetization which may interfere with packetization rates defined
in SDP or profile specific headers which require a fixed header size
greater than or equal to the specific Blocksize.


It may also be worth noting that even if a valid number is given for
Blocksize that the server would have to 're-packetize' the packet and
in most cases a packet CANNOT be re-packetized without re-packetizing
the entire frame where the packet was contained.


This adds an unnecessary delay and causes differentiation in reporting
to and from receivers especially in multicast situations.


It is therefore recommended that Blocksize be only used during a
'OPTIONS' or 'SETUP' request and if the server does not support the
given Blocksize that the status code returned be 'INFORMATIONAL' and
the Blocksize header in the response should indicate the minimum
required Blocksize.


-----------------


I would like to file this errata as soon as possible if everyone agrees;


If it's not erratum can we please also address this misnomer I seem to have.


Thank you!

--e89a8ff246ed1bee84050c3433b2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><pre class=3D"" style=3D"font-size:1em;margin-top:0px;marg=
in-bottom:0px;color:rgb(0,0,0)"><span class=3D"" style=3D"line-height:0pt;d=
isplay:inline;font-size:1em;font-weight:bold"><pre style=3D"font-weight:nor=
mal;line-height:normal;word-wrap:break-word;white-space:pre-wrap">Please se=
e the following two paragraphs regarding Blocksize.</pre><pre style=3D"font=
-weight:normal;line-height:normal;word-wrap:break-word;white-space:pre-wrap=
">12.7 Blocksize

   This request header field is sent from the client to the media server
   asking the server for a particular media packet size. This packet
   size does not include lower-layer headers such as IP, UDP, or RTP.
   The server is free to use a blocksize which is lower than the one
   requested. The server MAY truncate this packet size to the closest
   multiple of the minimum, media-specific block size, or override it
   with the media-specific size if necessary. The block size MUST be a
   positive decimal number, measured in octets. The server only returns
   an error (416) if the value is syntactically invalid.</pre><pre style=3D=
"font-weight:normal;line-height:normal;word-wrap:break-word;white-space:pre=
-wrap"><br></pre></span></pre><pre class=3D"" style=3D"font-size:1em;margin=
-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span class=3D"" style=3D"line=
-height:0pt;display:inline;font-size:1em;font-weight:bold"><h3 style=3D"lin=
e-height:0pt;display:inline;font-size:1em"><a class=3D"" name=3D"section-18=
.10" href=3D"http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#sec=
tion-18.10" style=3D"color:black;text-decoration:none">18.10</a>.  Blocksiz=
e</h3></span>

   The Blocksize request-header field is sent from the client to the
   media server asking the server for a particular media packet size.
   This packet size does not include lower-layer headers such as IP,
</pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0=
px;color:rgb(0,0,0)">   UDP, or RTP.  The server is free to use a blocksize=
 which is lower
   than the one requested.  The server MAY truncate this packet size to
   the closest multiple of the minimum, media-specific block size, or
   override it with the media-specific size if necessary.  The block
   size MUST be a positive decimal number, measured in octets.  The
   server only returns an error (4xx) if the value is syntactically
   invalid.</pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;marg=
in-bottom:0px;color:rgb(0,0,0)"><br></pre><pre class=3D"" style=3D"font-siz=
e:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Both paragraphs go=
 to specify that the number MUST be positive but specify no LOWER bound.</p=
re><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;=
color:rgb(0,0,0)"><br></pre><pre class=3D"" style=3D"font-size:1em;margin-t=
op:0px;margin-bottom:0px;color:rgb(0,0,0)">A Blocksize of 12 or less will c=
ause data loss under UDP and cause invalid framing under TCP.</pre><pre cla=
ss=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0=
,0,0)"><br></pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;marg=
in-bottom:0px;color:rgb(0,0,0)">A Blocksize of &gt;=3D 12 &lt;=3D 20 will c=
ause no payload data to be able to be sent in most profiles which utilize a=
 4 - 16 byte header.</pre><pre class=3D"" style=3D"font-size:1em;margin-top=
:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre class=3D"" style=3D=
"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Therefore=
 the minimum Blocksize must be 21 when RTP is in use and such a low number =
of octets in the payload (1) would cause unnecessary stain on the server.</=
pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px=
;color:rgb(0,0,0)"><br></pre><pre class=3D"" style=3D"font-size:1em;margin-=
top:0px;margin-bottom:0px;color:rgb(0,0,0)">It should be noted that the Blo=
cksize MUST be a positive decimal number greater than or equal to that supp=
orted by the underlying transport. </pre><pre class=3D"" style=3D"font-size=
:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre clas=
s=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,=
0,0)">This will prevent a client from undermining the MTU and attempting to=
 force a server to fragment packets against protocol rules OR perform re-pa=
cketization which may interfere with packetization rates defined in SDP or =
profile specific headers which require a fixed header size greater than or =
equal to the specific Blocksize.</pre><pre class=3D"" style=3D"font-size:1e=
m;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><pre class=3D"" style=3D"c=
olor:rgb(34,34,34);font-size:1em;margin-top:0px;margin-bottom:0px"><font co=
lor=3D"#000000"><span style=3D"font-size:1em">It may also be worth noting t=
hat even if a valid number is given for Blocksize that the server would hav=
e to &#39;re-packetize&#39; the packet and in most cases a packet CANNOT be=
 re-packetized without re-packetizing the entire frame where the packet was=
 contained.=C2=A0</span></font></pre><pre class=3D"" style=3D"color:rgb(34,=
34,34);font-size:1em;margin-top:0px;margin-bottom:0px"><font color=3D"#0000=
00"><span style=3D"font-size:1em"><br></span></font></pre><pre class=3D"" s=
tyle=3D"color:rgb(34,34,34);font-size:1em;margin-top:0px;margin-bottom:0px"=
><font color=3D"#000000"><span style=3D"font-size:1em">This adds an unneces=
sary delay and causes </span>differentiation<span style=3D"font-size:1em"> =
in reporting to and from receivers especially in multicast situations.</spa=
n></font></pre><pre class=3D"" style=3D"color:rgb(34,34,34);font-size:1em;m=
argin-top:0px;margin-bottom:0px"><font color=3D"#000000"><span style=3D"fon=
t-size:1em"><br></span></font></pre><pre class=3D"" style=3D"margin-top:0px=
;margin-bottom:0px"><font color=3D"#000000"><font color=3D"#222222"><span s=
tyle=3D"font-size:1em">It is therefore </span></font><span style=3D"font-si=
ze:10.5625px">recommended</span><font color=3D"#222222"><span style=3D"font=
-size:1em"> that Blocksize be only used during a &#39;OPTIONS&#39; or &#39;=
SETUP&#39; request and if the server does not support the given Blocksize t=
hat the status code returned be &#39;INFORMATIONAL&#39; and the Blocksize h=
eader in the response should indicate the minimum required Blocksize.</span=
></font></font></pre></pre><pre class=3D"" style=3D"font-size:1em;margin-to=
p:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre class=3D"" style=
=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">------=
-----------</pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;marg=
in-bottom:0px;color:rgb(0,0,0)"><br></pre><pre class=3D"" style=3D"font-siz=
e:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">I would like to fi=
le this errata as soon as possible if everyone agrees;</pre><pre class=3D""=
 style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">=
<br></pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bott=
om:0px;color:rgb(0,0,0)">If it&#39;s not erratum can we please also address=
 this misnomer I seem to have.</pre><pre class=3D"" style=3D"font-size:1em;=
margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre class=3D"=
" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"=
>Thank you!</pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"=
><br></pre></div>

--e89a8ff246ed1bee84050c3433b2--


From nobody Fri Jan  9 18:28:33 2015
Return-Path: <worley@alum.mit.edu>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54CF51A6FF0 for <avt@ietfa.amsl.com>; Fri,  9 Jan 2015 18:28:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k3sxIr50UCr6 for <avt@ietfa.amsl.com>; Fri,  9 Jan 2015 18:28:26 -0800 (PST)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 704F71A6F02 for <avt@ietf.org>; Fri,  9 Jan 2015 18:28:25 -0800 (PST)
Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-06v.sys.comcast.net with comcast id e2Tr1p0042VvR6D012UPkE; Sat, 10 Jan 2015 02:28:23 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-ch2-19v.sys.comcast.net with comcast id e2UP1p0051KKtkw012UPQd; Sat, 10 Jan 2015 02:28:23 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id t0A2SMF2026545; Fri, 9 Jan 2015 21:28:22 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id t0A2SMYw026542; Fri, 9 Jan 2015 21:28:22 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Julius Friedman <juliusfriedman@gmail.com>
In-Reply-To: <CACFvNHXwTm5k7Wiw65A=eSBEF9RqP4FJnNysziFik7vpnqrR4A@mail.gmail.com> (juliusfriedman@gmail.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Fri, 09 Jan 2015 21:28:22 -0500
Message-ID: <87r3v38j3t.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1420856903; bh=Q7Pfz1LSM914iCDd9q9DGw1vE/nWobp/18VqpaxnKhI=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=OoGNRGasNnrAIsRR7Ka7aiD+Gq7IwvA6XIi8oyqqRNpXq5dZidcV3g3GIPBdHwXor GxAoJg5Jjv8S6sCIESIt1KLaUwD/pIk1vzeoVF/GRQfz7ED8tFEsjAVP8M7S4Ahx6Z J/Rr1EQLcBpmrbIwPzYRGZUMhb+Y0FlF/wgeg9S1N60vV4+HQmNca2u0WpIGlM4ST/ 679IMrqk/bJZXr6FIDOvfht/QxgxzfrCe2GONS0VVIGfjPO42ILFyo1C4F09biv3ak iIeBzU/tIpONySo8OGTwR7l6QsFtUOeJe4cIKgrgNDRHXmZb2xlejb19qSR60en2dX pcGVgaiZeBDiA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/IBH8ruzhLIuuZWkks2bWxD1fDOc>
Cc: mmusic@ietf.org, avt@ietf.org
Subject: Re: [AVTCORE] New Possible Errata in RFC2326 (And Draft) regarding Blocksize
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Jan 2015 02:28:28 -0000

Julius Friedman <juliusfriedman@gmail.com> writes:
> 18.10 <http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#section-18.10>.
> Blocksize
>
>    The Blocksize request-header field is sent from the client to the
>    media server asking the server for a particular media packet size.
>    This packet size does not include lower-layer headers such as IP,
>    UDP, or RTP.  The server is free to use a blocksize which is lower
>    than the one requested.  The server MAY truncate this packet size to
>    the closest multiple of the minimum, media-specific block size, or
>    override it with the media-specific size if necessary.  The block
>    size MUST be a positive decimal number, measured in octets.  The
>    server only returns an error (4xx) if the value is syntactically
>    invalid.
>
> Both paragraphs go to specify that the number MUST be positive but
> specify no LOWER bound.
>
> A Blocksize of 12 or less will cause data loss under UDP and cause
> invalid framing under TCP.

Could you explain this in more detail?  Since the "Blocksize" number
"does not include lower-layer headers such as IP, UDP, or RTP", it seems
to me that it counts only the bytes after the "RTP Fixed Header Fields"
and any RTP header extensions, and that number legitimately could be
small (depending on the media encoding in the RTP).

> It should be noted that the Blocksize MUST be a positive decimal
> number greater than or equal to that supported by the underlying
> transport.

In any case, *this* RFC does not *have* to state that, as that is a
requirement imposed by other RFCs. 

> I would like to file this errata as soon as possible if everyone agrees;
>
> If it's not erratum can we please also address this misnomer I seem to have.

As far as I can tell, it's not an erratum, because there is no "error"
in the RFC.  What you're suggesting is that there is useful information
that the RFC does not include, but that information is not an error in
this RFC's text.

Dale


From nobody Fri Jan  9 19:25:15 2015
Return-Path: <worley@alum.mit.edu>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E409A1A8BC3 for <avt@ietfa.amsl.com>; Fri,  9 Jan 2015 19:25:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iFeFrRd42aDE for <avt@ietfa.amsl.com>; Fri,  9 Jan 2015 19:25:05 -0800 (PST)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28FEF1A1B43 for <avt@ietf.org>; Fri,  9 Jan 2015 19:25:04 -0800 (PST)
Received: from resomta-ch2-03v.sys.comcast.net ([69.252.207.99]) by resqmta-ch2-06v.sys.comcast.net with comcast id e3R41p00129Cfhx013R4uC; Sat, 10 Jan 2015 03:25:04 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-ch2-03v.sys.comcast.net with comcast id e3R21p00F1KKtkw013R3CT; Sat, 10 Jan 2015 03:25:03 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id t0A3P0ia001530; Fri, 9 Jan 2015 22:25:00 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id t0A3Ox3k001526; Fri, 9 Jan 2015 22:24:59 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Julius Friedman <juliusfriedman@gmail.com>
In-Reply-To: <CACFvNHVkDBXfPKaAk1V8N+XRSfLg4-snWWbbLxJb2w7W97ZzJg@mail.gmail.com> (juliusfriedman@gmail.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Fri, 09 Jan 2015 22:24:59 -0500
Message-ID: <87k30v8ghg.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1420860304; bh=L/TTBGAhJhlZSO89Au9FfIzYF69TrcnQ03742N8Z3EI=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=oFCr/bUIKkJ2B82/470iP42NrFfD4snjBSW5b5jfMdjgUCdo42LbGqffkIObSLy4j I+jdUIbi9Ja9sdetzfr3zXcoX4UsyPW+G0cZKnT96wKNZh+oE2eBzIDC18/ykwplNm MXRcg9o4nnEbyQGGphikJcpsVohCPbzg4guJ+7bA0Qmuukq0cPnF9lwaagOsnRLbJ8 Hg1nV2Kg8njXqIdjgZA17zSHU8ZiXtCSVTaN7lJSJ4Xh6/LD7anU10JPlPdZk5l9sy q231o6+DE/qOt4G14cHquOAJ8IG6YCnzST6FlRvkXHRUt66fud79pwCPfVACO+8YYW Au2NaOkDX4Qnw==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/vM4MmTRpDnpsaAqf50HdkEX4I5w>
Cc: avt@ietf.org, mmusic@ietf.org
Subject: Re: [AVTCORE] [MMUSIC]  Question - Erratum 4097
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Jan 2015 03:25:07 -0000

Julius Friedman <juliusfriedman@gmail.com> writes:
> The RFC only provided a way for certain sized images much lower then what
> JPEG supports to be transferred, this erratum fixes this by specifying that
> in some cases you may need to use a different fraction to obtain the height
> (which might not be in a multiple of 16 anyway) additionally it allows one
> to deal with the nuance that if the data is so large that the
> FragmentOffset will probably overflow during this time and provides a way
> to deal with that as well.

Whew, you're going to have to slow down here.  I'm not tracking what you
say very well, but if I read it correctly, you're saying you want to
change the divisor in sections 3.1.5 and 3.1.6 from 8 to 256.  Is that
really correct?  And your justification seems to be that there are JPEGs
that are so large that their sizes can't be represented within an 8 bit
field with a multiplier of 8 (i.e., >2048).

If so, this isn't an erratum, but a technical change, and it would have
to go through the working group as an update to the RFC.  It would also
be incompatible with every implementation that now uses this feature.

In regard to "Fragment Offset", you seem to be allowing for JPEGs in
excess of 2^24 bytes, which seems to me to be unlikely within the
constraints of the existing height and width limitations.  In any case,
reducing Fragment Offset modulo 2^24 would make reassembly of large
frames ambiguous -- you'd really need a larger Fragment Offset field.

What you're really asking for here is an RTP payload format much like
RFC 2435 but different from it and incompatible with it.  That would be
a new piece of work, as well as requiring assignment of a new "encoding
name" so that control protocols could specify it.  (The "JPEG" encoding
name is assigned to RFC 2435 media by RFC 3551 section 5.2.)

Errata aren't for situations where "I think this protocol could have
been designed better", but where the *text* doesn't express what the
working group *meant*.

Dale


From nobody Fri Jan  9 19:38:46 2015
Return-Path: <juliusfriedman@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D31261A7034; Fri,  9 Jan 2015 19:38:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GcBoXUYNjsug; Fri,  9 Jan 2015 19:38:36 -0800 (PST)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 587AA1A70FE; Fri,  9 Jan 2015 19:38:36 -0800 (PST)
Received: by mail-pd0-f172.google.com with SMTP id y13so20806959pdi.3; Fri, 09 Jan 2015 19:38:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9CkH4U1Pc2Nwro3YLKticxN09IF7x6FHbe57i/0GYhc=; b=EgDkX0pcceMttn4ObtnXL31ERFZK6D5RSFQH9ZpRKk5RWGVfG6PpgQyMq+wXfhUTjy kufJ5EB9zR88PbMQOLjL9qdMRnVzgqL5NKlLhU33D+MhYghmadZhVHwdT2vMQYNDv3E+ lL1aI0/W6wSEoR87eJnHwRdYM7nikls4NSNGH83dXdV5DhIrCVevZkuXPkGcqOGMHabG MPFjlo24+z9/WmVL7o+Neeax1+/2gTHDgklZ2tb/1fOFxCIksX0zczmMOi+YWwljkviQ g1XnVkGR9zV6VAlR06Qg9i4Mm5BrJMLmqmHx9/+heL9BjM9wg61f5veFaUD3nY1TI+03 7yMQ==
MIME-Version: 1.0
X-Received: by 10.68.236.67 with SMTP id us3mr27729223pbc.121.1420861115542; Fri, 09 Jan 2015 19:38:35 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Fri, 9 Jan 2015 19:38:35 -0800 (PST)
In-Reply-To: <87r3v38j3t.fsf@hobgoblin.ariadne.com>
References: <CACFvNHXwTm5k7Wiw65A=eSBEF9RqP4FJnNysziFik7vpnqrR4A@mail.gmail.com> <87r3v38j3t.fsf@hobgoblin.ariadne.com>
Date: Fri, 9 Jan 2015 22:38:35 -0500
Message-ID: <CACFvNHXyCbQgx3jtzShSQGT9H-TD_Wz7bEkyOB2zfQNjof1VZw@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary=047d7b2e11b1114d2e050c44021e
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/vfHKeltDHOrKeyCxz6Z9UoTmOlw>
Cc: mmusic@ietf.org, avt@ietf.org
Subject: Re: [AVTCORE] New Possible Errata in RFC2326 (And Draft) regarding Blocksize
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Jan 2015 03:38:40 -0000

--047d7b2e11b1114d2e050c44021e
Content-Type: text/plain; charset=UTF-8

...

", it seems
to me that it counts only the bytes after the "RTP Fixed Header Fields"
and any RTP header extensions, and that number legitimately could be
small (depending on the media encoding in the RTP).
"

- There must be 12 octets which are the fixed header, this is where that
information comes from.

- If ROHC is used or some other encoding / compression which changes this
amount it is beyond the scope of RTP and that is why I say that the
underlying Transport should handle this.

We are not talking about other RFC's we are talking about the ones which
state the information (RFC2326 and it's biz draft), they introduce this
header and thus should concretely define it's functionality such that it
does not impose upon other requirements.

I am confused as how can you both say you don't understand and that there
is no error? It has now been explained further... Please re-consider, you
omitted to respond to other points within the same email chain which relate
to the problem so it imposes upon my response and would cause me to repeat
data here again which I was asked not to before.

If there is a better mechanism for communication of these issues please let
me know, I would be happy to prepare a summary and present it either as a
document or over a tele-conference to address this as well as any other
points which have yet to be addressed.

If there is no error then what is the process to include this useful
information in some way so that others may know as well?

I sincerely appreciate your time,
Julius



On Fri, Jan 9, 2015 at 9:28 PM, Dale R. Worley <worley@ariadne.com> wrote:

> Julius Friedman <juliusfriedman@gmail.com> writes:
> > 18.10 <
> http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#section-18.10>.
> > Blocksize
> >
> >    The Blocksize request-header field is sent from the client to the
> >    media server asking the server for a particular media packet size.
> >    This packet size does not include lower-layer headers such as IP,
> >    UDP, or RTP.  The server is free to use a blocksize which is lower
> >    than the one requested.  The server MAY truncate this packet size to
> >    the closest multiple of the minimum, media-specific block size, or
> >    override it with the media-specific size if necessary.  The block
> >    size MUST be a positive decimal number, measured in octets.  The
> >    server only returns an error (4xx) if the value is syntactically
> >    invalid.
> >
> > Both paragraphs go to specify that the number MUST be positive but
> > specify no LOWER bound.
> >
> > A Blocksize of 12 or less will cause data loss under UDP and cause
> > invalid framing under TCP.
>
> Could you explain this in more detail?  Since the "Blocksize" number
> "does not include lower-layer headers such as IP, UDP, or RTP", it seems
> to me that it counts only the bytes after the "RTP Fixed Header Fields"
> and any RTP header extensions, and that number legitimately could be
> small (depending on the media encoding in the RTP).
>
> > It should be noted that the Blocksize MUST be a positive decimal
> > number greater than or equal to that supported by the underlying
> > transport.
>
> In any case, *this* RFC does not *have* to state that, as that is a
> requirement imposed by other RFCs.
>
> > I would like to file this errata as soon as possible if everyone agrees;
> >
> > If it's not erratum can we please also address this misnomer I seem to
> have.
>
> As far as I can tell, it's not an erratum, because there is no "error"
> in the RFC.  What you're suggesting is that there is useful information
> that the RFC does not include, but that information is not an error in
> this RFC's text.
>
> Dale
>

--047d7b2e11b1114d2e050c44021e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>...</div><div><br></div>&quot;,<span style=3D"font-si=
ze:12.8000001907349px">=C2=A0it seems</span><br style=3D"font-size:12.80000=
01907349px"><span style=3D"font-size:12.8000001907349px">to me that it coun=
ts only the bytes after the &quot;RTP Fixed Header Fields&quot;</span><br s=
tyle=3D"font-size:12.8000001907349px"><span style=3D"font-size:12.800000190=
7349px">and any RTP header extensions, and that number legitimately could b=
e</span><br style=3D"font-size:12.8000001907349px"><span style=3D"font-size=
:12.8000001907349px">small (depending on the media encoding in the RTP).</s=
pan><div><span style=3D"font-size:12.8000001907349px">&quot;</span></div><d=
iv><br></div><div><span style=3D"font-size:12.8000001907349px">-=C2=A0</spa=
n><span style=3D"font-size:12.8000001907349px">There must be 12 octets whic=
h are the fixed header, this is where that information comes from.</span></=
div><div><span style=3D"font-size:12.8000001907349px"><br></span></div><div=
><span style=3D"font-size:12.8000001907349px">- If ROHC is used or some oth=
er encoding / compression which changes this amount it is beyond the scope =
of RTP and that is why I say that the underlying Transport should handle th=
is.</span></div><div><span style=3D"font-size:12.8000001907349px"><br></spa=
n></div><div><span style=3D"font-size:12.8000001907349px">We are not talkin=
g about other RFC&#39;s we are talking about the ones which state the infor=
mation (RFC2326 and it&#39;s biz draft), they introduce this header and thu=
s should concretely define it&#39;s functionality such that it does not imp=
ose upon other requirements.</span></div><div><span style=3D"font-size:12.8=
000001907349px"><br></span></div><div><span style=3D"font-size:12.800000190=
7349px">I am confused as how can you both say you don&#39;t understand and =
that there is no error? It has now been explained further... Please re-cons=
ider, you omitted to respond to other points within the same email chain wh=
ich relate to the problem so it imposes upon my response and would cause me=
 to repeat data here again which I was asked not to before.</span></div><di=
v><span style=3D"font-size:12.8000001907349px"><br></span></div><div><span =
style=3D"font-size:12.8000001907349px">If there is a better mechanism for c=
ommunication of these issues please let me know, I would be happy to prepar=
e a summary and present it either as a document or over a tele-conference t=
o address this as well as any other points which have yet to be addressed.<=
/span></div><div><span style=3D"font-size:12.8000001907349px"><br></span></=
div><div><span style=3D"font-size:12.8000001907349px">If there is no error =
then what is the process to include this useful information in some way so =
that others may know as well?=C2=A0</span></div><div><span style=3D"font-si=
ze:12.8000001907349px"><br></span></div><div><span style=3D"font-size:12.80=
00001907349px">I sincerely=C2=A0appreciate</span><span style=3D"font-size:1=
2.8000001907349px">=C2=A0your time,</span><span style=3D"font-size:12.80000=
01907349px"><br></span></div><div>Julius</div><div><span style=3D"font-size=
:12.8000001907349px"><br></span></div><div><span style=3D"font-size:12.8000=
001907349px"><br></span></div></div><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Fri, Jan 9, 2015 at 9:28 PM, Dale R. Worley <span dir=
=3D"ltr">&lt;<a href=3D"mailto:worley@ariadne.com" target=3D"_blank">worley=
@ariadne.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Julius=
 Friedman &lt;<a href=3D"mailto:juliusfriedman@gmail.com">juliusfriedman@gm=
ail.com</a>&gt; writes:<br>
&gt; 18.10 &lt;<a href=3D"http://tools.ietf.org/html/draft-ietf-mmusic-rfc2=
326bis-40#section-18.10" target=3D"_blank">http://tools.ietf.org/html/draft=
-ietf-mmusic-rfc2326bis-40#section-18.10</a>&gt;.<br>
<span class=3D"">&gt; Blocksize<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 The Blocksize request-header field is sent from the clien=
t to the<br>
&gt;=C2=A0 =C2=A0 media server asking the server for a particular media pac=
ket size.<br>
&gt;=C2=A0 =C2=A0 This packet size does not include lower-layer headers suc=
h as IP,<br>
&gt;=C2=A0 =C2=A0 UDP, or RTP.=C2=A0 The server is free to use a blocksize =
which is lower<br>
&gt;=C2=A0 =C2=A0 than the one requested.=C2=A0 The server MAY truncate thi=
s packet size to<br>
&gt;=C2=A0 =C2=A0 the closest multiple of the minimum, media-specific block=
 size, or<br>
&gt;=C2=A0 =C2=A0 override it with the media-specific size if necessary.=C2=
=A0 The block<br>
&gt;=C2=A0 =C2=A0 size MUST be a positive decimal number, measured in octet=
s.=C2=A0 The<br>
&gt;=C2=A0 =C2=A0 server only returns an error (4xx) if the value is syntac=
tically<br>
&gt;=C2=A0 =C2=A0 invalid.<br>
&gt;<br>
&gt; Both paragraphs go to specify that the number MUST be positive but<br>
&gt; specify no LOWER bound.<br>
&gt;<br>
&gt; A Blocksize of 12 or less will cause data loss under UDP and cause<br>
&gt; invalid framing under TCP.<br>
<br>
</span>Could you explain this in more detail?=C2=A0 Since the &quot;Blocksi=
ze&quot; number<br>
&quot;does not include lower-layer headers such as IP, UDP, or RTP&quot;, i=
t seems<br>
to me that it counts only the bytes after the &quot;RTP Fixed Header Fields=
&quot;<br>
and any RTP header extensions, and that number legitimately could be<br>
small (depending on the media encoding in the RTP).<br>
<span class=3D""><br>
&gt; It should be noted that the Blocksize MUST be a positive decimal<br>
&gt; number greater than or equal to that supported by the underlying<br>
&gt; transport.<br>
<br>
</span>In any case, *this* RFC does not *have* to state that, as that is a<=
br>
requirement imposed by other RFCs.<br>
<span class=3D""><br>
&gt; I would like to file this errata as soon as possible if everyone agree=
s;<br>
&gt;<br>
&gt; If it&#39;s not erratum can we please also address this misnomer I see=
m to have.<br>
<br>
</span>As far as I can tell, it&#39;s not an erratum, because there is no &=
quot;error&quot;<br>
in the RFC.=C2=A0 What you&#39;re suggesting is that there is useful inform=
ation<br>
that the RFC does not include, but that information is not an error in<br>
this RFC&#39;s text.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Dale<br>
</font></span></blockquote></div><br></div>

--047d7b2e11b1114d2e050c44021e--


From nobody Fri Jan  9 19:49:48 2015
Return-Path: <juliusfriedman@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9368A1A710C; Fri,  9 Jan 2015 19:49:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W4oxOcHPzBDA; Fri,  9 Jan 2015 19:49:43 -0800 (PST)
Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A348B1A70FE; Fri,  9 Jan 2015 19:49:43 -0800 (PST)
Received: by mail-pd0-f177.google.com with SMTP id ft15so20784039pdb.8; Fri, 09 Jan 2015 19:49:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=uGBfFRVLw4Za/Y5e4WOUyJQtesi+Gjk7cX6Q7EkzgCQ=; b=rPVgqC2EFKBxUTxgTi0Mf9gKxpSn0eXrQfMyPmJnpcdZjbCcALDYf/Olmggn2GvNgL sSMkYYmZpXA5DqjNCCwKhOibp6B9/ZGDBw1e3aYqQAMv126Sb0GIe0XT4SdEAOTuT4fL CCMgsWCZugE5cAxONsHZYel4cI7O4k9cY5tN57/RUHeg/39ewJSQ7hF8C6KuPO+qz239 PZnDZnvHeKYIDZCdW6oNGppQLaSNkQcZWzLOdeufX3GO29D4rLmTGxulWRsQ1Kotm8Ie kKbEPoE7XbZawc2QBNLspXz4XA4L0ePt6fB05Xk3+OIAUVo8jBPXP8S/bJ09KFCQgX6l dvtg==
MIME-Version: 1.0
X-Received: by 10.66.90.130 with SMTP id bw2mr28309647pab.56.1420861782940; Fri, 09 Jan 2015 19:49:42 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Fri, 9 Jan 2015 19:49:42 -0800 (PST)
In-Reply-To: <87k30v8ghg.fsf@hobgoblin.ariadne.com>
References: <CACFvNHVkDBXfPKaAk1V8N+XRSfLg4-snWWbbLxJb2w7W97ZzJg@mail.gmail.com> <87k30v8ghg.fsf@hobgoblin.ariadne.com>
Date: Fri, 9 Jan 2015 22:49:42 -0500
Message-ID: <CACFvNHWKMVHceL5PrKozLDWE9-ppXybiP0B7b2C_Lfh9yBBaKQ@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>, avt@ietf.org, mmusic@ietf.org
Content-Type: multipart/alternative; boundary=001a11c2c608d8e2fe050c4429f6
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/q7ScL4FjCaCY6yBh_4PqifoZmkE>
Subject: Re: [AVTCORE] [MMUSIC] Question - Erratum 4097
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Jan 2015 03:49:46 -0000

--001a11c2c608d8e2fe050c4429f6
Content-Type: text/plain; charset=UTF-8

What about another divisor and or some text which states that if there is a
modulo that the frame height may have to be computed alternately? The issue
is also for black and white images and situations where 1 or more than 2
quantization tables were used.. I included samples of those images in the
initial email to the IETF which were from the JPEG test suite the W3C used
and I can re-attach them if required, there is nothing "special" about them
other than the fact that:

1) they are not sized correctly after depacketization due to the size
constraint which makes ANY image which is not sized in multiples of 8
either larger or smaller which DOES effect decoding quality.
2) they do not display correctly due to a missing table or a absent table.

The fact that the header is fixed can probably be used to the advantage to
either use the MBZ in such a case or the DRI fields if it's not being used
BUT I think that is more complex and IT DOES make it incompatible, if the
FragmentOffset is used like I stated it WILL be compatible with existing
implementations and no change will be required. I know that larger field is
desirable but the 'trick' used does allow compatibility and correctly
sorting the offsets and obtaining their correct value during this 'roll
over' which is unlikely as you stated anyway and thus only given for such
cases as those....

The fact that the image is incorrect makes this errata, the fact that the
verbiage in the RFC also allows for  via (RFC2435)

4.1 <https://tools.ietf.org/html/rfc2435#section-4.1>.  The Type Field


Which makes this erratum because images which are advertised as supported
cannot be viewed or are distorted when the "reference" code is to be used
with such images and is NOT stated in the RFC....

Please advise.

On Fri, Jan 9, 2015 at 10:24 PM, Dale R. Worley <worley@ariadne.com> wrote:

> Julius Friedman <juliusfriedman@gmail.com> writes:
> > The RFC only provided a way for certain sized images much lower then what
> > JPEG supports to be transferred, this erratum fixes this by specifying
> that
> > in some cases you may need to use a different fraction to obtain the
> height
> > (which might not be in a multiple of 16 anyway) additionally it allows
> one
> > to deal with the nuance that if the data is so large that the
> > FragmentOffset will probably overflow during this time and provides a way
> > to deal with that as well.
>
> Whew, you're going to have to slow down here.  I'm not tracking what you
> say very well, but if I read it correctly, you're saying you want to
> change the divisor in sections 3.1.5 and 3.1.6 from 8 to 256.  Is that
> really correct?  And your justification seems to be that there are JPEGs
> that are so large that their sizes can't be represented within an 8 bit
> field with a multiplier of 8 (i.e., >2048).
>
> If so, this isn't an erratum, but a technical change, and it would have
> to go through the working group as an update to the RFC.  It would also
> be incompatible with every implementation that now uses this feature.
>
> In regard to "Fragment Offset", you seem to be allowing for JPEGs in
> excess of 2^24 bytes, which seems to me to be unlikely within the
> constraints of the existing height and width limitations.  In any case,
> reducing Fragment Offset modulo 2^24 would make reassembly of large
> frames ambiguous -- you'd really need a larger Fragment Offset field.
>
> What you're really asking for here is an RTP payload format much like
> RFC 2435 but different from it and incompatible with it.  That would be
> a new piece of work, as well as requiring assignment of a new "encoding
> name" so that control protocols could specify it.  (The "JPEG" encoding
> name is assigned to RFC 2435 media by RFC 3551 section 5.2.)
>
> Errata aren't for situations where "I think this protocol could have
> been designed better", but where the *text* doesn't express what the
> working group *meant*.
>
> Dale
>

--001a11c2c608d8e2fe050c4429f6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">What about another divisor and or some text which states t=
hat if there is a modulo that the frame height may have to be computed alte=
rnately? The issue is also for black and white images and situations where =
1 or more than 2 quantization tables were used.. I included samples of thos=
e images in the initial email to the IETF which were from the JPEG test sui=
te the W3C used and I can re-attach them if required, there is nothing &quo=
t;special&quot; about them other than the fact that:<div><br></div><div>1) =
they are not sized correctly after depacketization due to the size constrai=
nt which makes ANY image which is not sized in multiples of 8 either larger=
 or smaller which DOES effect decoding quality.=C2=A0</div><div>2) they do =
not display correctly due to a missing table or a absent table.</div><div><=
br></div><div>The fact that the header is fixed can probably be used to the=
 advantage to either use the MBZ in such a case or the DRI fields if it&#39=
;s not being used BUT I think that is more complex and IT DOES make it inco=
mpatible, if the FragmentOffset is used like I stated it WILL be compatible=
 with existing implementations and no change will be required. I know that =
larger field is desirable but the &#39;trick&#39; used does allow compatibi=
lity and correctly sorting the offsets and obtaining their correct value du=
ring this &#39;roll over&#39; which is unlikely as you stated anyway and th=
us only given for such cases as those....</div><div><br></div><div>The fact=
 that the image is incorrect makes this errata, the fact that the verbiage =
in the RFC also allows for =C2=A0via (RFC2435)<br></div><div><br></div><div=
><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;co=
lor:rgb(0,0,0)"><span class=3D"" style=3D"line-height:0pt;display:inline;fo=
nt-size:1em;font-weight:bold"><h3 style=3D"line-height:0pt;display:inline;f=
ont-size:1em"><a class=3D"" name=3D"section-4.1" href=3D"https://tools.ietf=
.org/html/rfc2435#section-4.1" style=3D"color:black;text-decoration:none">4=
.1</a>.  The Type Field</h3></span>
</pre></div><div><span class=3D"" style=3D"line-height:0pt;display:inline;f=
ont-size:1em;font-weight:bold"><h3 style=3D"line-height:0pt;display:inline;=
font-size:1em"><br></h3></span></div><div><span class=3D"" style=3D"display=
:inline"><h3 style=3D"display:inline"><font><span style=3D"font-weight:norm=
al">Which makes this=C2=A0erratum=C2=A0because images which are advertised =
as supported cannot be viewed or are distorted when the &quot;reference&quo=
t; code is to be used with such images and is NOT stated in the RFC....</sp=
an></font><br></h3></span></div><div><span class=3D"" style=3D"display:inli=
ne"><h3 style=3D"display:inline"><font><span style=3D"font-weight:normal"><=
br></span></font></h3></span></div><div><span class=3D"" style=3D"display:i=
nline"><h3 style=3D"display:inline"><font><span style=3D"font-weight:normal=
">Please advise.</span></font></h3></span></div></div><div class=3D"gmail_e=
xtra"><br><div class=3D"gmail_quote">On Fri, Jan 9, 2015 at 10:24 PM, Dale =
R. Worley <span dir=3D"ltr">&lt;<a href=3D"mailto:worley@ariadne.com" targe=
t=3D"_blank">worley@ariadne.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Julius Friedman &lt;<a href=3D"mailto:juliusfriedman@gmail.co=
m">juliusfriedman@gmail.com</a>&gt; writes:<br>
&gt; The RFC only provided a way for certain sized images much lower then w=
hat<br>
&gt; JPEG supports to be transferred, this erratum fixes this by specifying=
 that<br>
&gt; in some cases you may need to use a different fraction to obtain the h=
eight<br>
&gt; (which might not be in a multiple of 16 anyway) additionally it allows=
 one<br>
&gt; to deal with the nuance that if the data is so large that the<br>
&gt; FragmentOffset will probably overflow during this time and provides a =
way<br>
&gt; to deal with that as well.<br>
<br>
Whew, you&#39;re going to have to slow down here.=C2=A0 I&#39;m not trackin=
g what you<br>
say very well, but if I read it correctly, you&#39;re saying you want to<br=
>
change the divisor in sections 3.1.5 and 3.1.6 from 8 to 256.=C2=A0 Is that=
<br>
really correct?=C2=A0 And your justification seems to be that there are JPE=
Gs<br>
that are so large that their sizes can&#39;t be represented within an 8 bit=
<br>
field with a multiplier of 8 (i.e., &gt;2048).<br>
<br>
If so, this isn&#39;t an erratum, but a technical change, and it would have=
<br>
to go through the working group as an update to the RFC.=C2=A0 It would als=
o<br>
be incompatible with every implementation that now uses this feature.<br>
<br>
In regard to &quot;Fragment Offset&quot;, you seem to be allowing for JPEGs=
 in<br>
excess of 2^24 bytes, which seems to me to be unlikely within the<br>
constraints of the existing height and width limitations.=C2=A0 In any case=
,<br>
reducing Fragment Offset modulo 2^24 would make reassembly of large<br>
frames ambiguous -- you&#39;d really need a larger Fragment Offset field.<b=
r>
<br>
What you&#39;re really asking for here is an RTP payload format much like<b=
r>
RFC 2435 but different from it and incompatible with it.=C2=A0 That would b=
e<br>
a new piece of work, as well as requiring assignment of a new &quot;encodin=
g<br>
name&quot; so that control protocols could specify it.=C2=A0 (The &quot;JPE=
G&quot; encoding<br>
name is assigned to RFC 2435 media by RFC 3551 section 5.2.)<br>
<br>
Errata aren&#39;t for situations where &quot;I think this protocol could ha=
ve<br>
been designed better&quot;, but where the *text* doesn&#39;t express what t=
he<br>
working group *meant*.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Dale<br>
</font></span></blockquote></div><br></div>

--001a11c2c608d8e2fe050c4429f6--


From nobody Sun Jan 18 11:33:34 2015
Return-Path: <juliusfriedman@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 992F41ACDF4; Sun, 18 Jan 2015 11:33:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id opf1zxFMOEYh; Sun, 18 Jan 2015 11:33:31 -0800 (PST)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA3371ACDF8; Sun, 18 Jan 2015 11:33:30 -0800 (PST)
Received: by mail-pd0-f169.google.com with SMTP id z10so32315610pdj.0; Sun, 18 Jan 2015 11:33:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=JmG0IH5hHX7DWvG/jQrkoxi1x5csQPYAl6RDActu4XY=; b=OtoVX5J8rliFa304HklPgSHLrxO40Wux7hblCpllLqLEcGHXwouHWLEnEZ19deWN3s Jei7HEPJQ4GLYp2hEf8nntN9V7Gwt/rHJxBmo5eumNsrrLbtFhEz6dyYy1DWiX/B9OKW nIK1fuZ+dWuY0D3Zd1XeHQRhWpj3K5uYR4maLzU+WrZ64Yteha89Ge4nZ4KZZpI5TgqP fDb7Zg/c6jbVgnU9SUBs0lqd/FiMh1PeZtpkJ8Un1YmQ2hnKiS5/cepH8uhfkKkJgSZG qgvknqYwwjkpZaBmRg4pCjxAUKRn/Q3qqmE1QjiIQZgBLTRURSxvjCNeLA0Bq4aG3nnk hOyQ==
MIME-Version: 1.0
X-Received: by 10.70.22.227 with SMTP id h3mr38904429pdf.160.1421609610062; Sun, 18 Jan 2015 11:33:30 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Sun, 18 Jan 2015 11:33:30 -0800 (PST)
Date: Sun, 18 Jan 2015 14:33:30 -0500
Message-ID: <CACFvNHVFUe7jHEK00ja3Vppi5GYeKptOuVPi97HrYU3DdiyLCA@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: mmusic@ietf.org, avt@ietf.org
Content-Type: multipart/alternative; boundary=047d7b6da18ad13458050cf2472f
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/pUuHiDlRvqscNyqNiAZ7QZxndGU>
Subject: [AVTCORE] On RFC2326
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Jan 2015 19:33:32 -0000

--047d7b6da18ad13458050cf2472f
Content-Type: text/plain; charset=UTF-8

Unfortunately I have more information which I have found to be
contradictory and possibly erratum.

Quite Succinctly,

"

10.7 <https://tools.ietf.org/html/rfc2326#section-10.7> TEARDOWN

   The TEARDOWN request stops the stream delivery for the given URI,
   freeing the resources associated with it. If the URI is the
   presentation URI for this presentation, any RTSP session identifier
   associated with the session is no longer valid. Unless all transport
   parameters are defined by the session description, a SETUP request
   has to be issued before the session can be played again.

"


However earlier in the document.


"

10.4 <https://tools.ietf.org/html/rfc2326#section-10.4> SETUP

....


The server generates session identifiers in response to SETUP
   requests. If a SETUP request to a server includes a session
   identifier, the server MUST bundle this setup request into the

   existing session or return error "459 Aggregate Operation Not
   Allowed" (see Section 11.3.10
<https://tools.ietf.org/html/rfc2326#section-11.3.10>).

"


If a users obtains a session Id related to an aggregate controlled
media and only one of the sub sessions received a "TEARDOWN" then the
RFC makes the server incorrectly remove the SessionId which is still
being used for the other sub-sessions.



The draft doesn't do any better in making this clearer IMHO.


Please advise,


I will also probably be filling more errata unless I can be directed
on how to properly convey the information without filling it.


I hope all else is well as I STILL haven't heard back from anyone
regarding both the clarifications I made. (Which is pretty ridiculous,
it's been over 2 years I have been asking these questions almost)


-Julius

--047d7b6da18ad13458050cf2472f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Unfortunately I have more information which I have found t=
o be contradictory and possibly erratum.<div><br></div><div><div>Quite Succ=
inctly,</div></div><div><br></div><div>&quot;</div><div><pre class=3D"" sty=
le=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><spa=
n class=3D"" style=3D"line-height:0pt;display:inline;font-size:1em;font-wei=
ght:bold"><h3 style=3D"line-height:0pt;display:inline;font-size:1em"><a cla=
ss=3D"" name=3D"section-10.7" href=3D"https://tools.ietf.org/html/rfc2326#s=
ection-10.7" style=3D"color:black;text-decoration:none">10.7</a> TEARDOWN</=
h3></span>

   The TEARDOWN request stops the stream delivery for the given URI,
   freeing the resources associated with it. If the URI is the
   presentation URI for this presentation, any RTSP session identifier
   associated with the session is no longer valid. Unless all transport
   parameters are defined by the session description, a SETUP request
   has to be issued before the session can be played again.</pre><pre class=
=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0=
,0)">&quot;</pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;marg=
in-bottom:0px;color:rgb(0,0,0)"><span style=3D"font-family:arial,sans-serif=
;font-size:small;color:rgb(34,34,34)"><br></span></pre><pre class=3D"" styl=
e=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span=
 style=3D"font-family:arial,sans-serif;font-size:small;color:rgb(34,34,34)"=
>However earlier in the document.</span></pre><pre class=3D"" style=3D"font=
-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span style=3D=
"font-family:arial,sans-serif;font-size:small;color:rgb(34,34,34)"><br></sp=
an></pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-botto=
m:0px;color:rgb(0,0,0)"><span style=3D"font-family:arial,sans-serif;font-si=
ze:small;color:rgb(34,34,34)">&quot;</span></pre><pre class=3D"" style=3D"f=
ont-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><pre class=
=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><span class=
=3D"" style=3D"line-height:0pt;display:inline;font-size:1em;font-weight:bol=
d"><h3 style=3D"line-height:0pt;display:inline;font-size:1em"><a class=3D""=
 name=3D"section-10.4" href=3D"https://tools.ietf.org/html/rfc2326#section-=
10.4" style=3D"color:black;text-decoration:none">10.4</a> SETUP</h3></span>=
</pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0=
px"><span class=3D"" style=3D"line-height:0pt;display:inline;font-size:1em;=
font-weight:bold"><h3 style=3D"line-height:0pt;display:inline;font-size:1em=
">....</h3></span></pre><pre class=3D"" style=3D"font-size:1em;margin-top:0=
px;margin-bottom:0px"><span class=3D"" style=3D"line-height:0pt;display:inl=
ine;font-size:1em;font-weight:bold"><h3 style=3D"line-height:0pt;display:in=
line;font-size:1em"><br></h3></span></pre></pre><pre class=3D"" style=3D"fo=
nt-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><pre class=
=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px">The server g=
enerates session identifiers in response to SETUP
   requests. If a SETUP request to a server includes a session
   identifier, the server MUST bundle this setup request into the</pre><pre=
 class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px">   exi=
sting session or return error &quot;459 Aggregate Operation Not
   Allowed&quot; (see <a href=3D"https://tools.ietf.org/html/rfc2326#sectio=
n-11.3.10">Section 11.3.10</a>).</pre></pre><pre class=3D"" style=3D"font-s=
ize:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span style=3D"f=
ont-family:arial,sans-serif;font-size:small;color:rgb(34,34,34)">&quot;</sp=
an></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font f=
ace=3D"arial, sans-serif"><br></font></pre><pre class=3D"" style=3D"margin-=
top:0px;margin-bottom:0px"><font face=3D"arial, sans-serif">If a users obta=
ins a session Id related to an aggregate controlled media and only one of t=
he sub sessions received a &quot;TEARDOWN&quot; then the RFC makes the serv=
er incorrectly remove the SessionId which is still being used for the other=
 sub-sessions.</font></pre><pre class=3D"" style=3D"margin-top:0px;margin-b=
ottom:0px"><br></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:=
0px"><br></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px">T=
he draft doesn&#39;t do any better in making this clearer IMHO.</pre><pre c=
lass=3D"" style=3D"margin-top:0px;margin-bottom:0px"><br></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px">Please advise,</pre><pre c=
lass=3D"" style=3D"margin-top:0px;margin-bottom:0px"><br></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px">I will also probably be fi=
lling more errata unless I can be directed on how to properly convey the in=
formation without filling it.</pre><pre class=3D"" style=3D"margin-top:0px;=
margin-bottom:0px"><br></pre><pre class=3D"" style=3D"margin-top:0px;margin=
-bottom:0px">I hope all else is well as I STILL haven&#39;t heard back from=
 anyone regarding both the clarifications I made. (Which is pretty ridiculo=
us, it&#39;s been over 2 years I have been asking these questions almost)</=
pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><br></pre><p=
re class=3D"" style=3D"margin-top:0px;margin-bottom:0px">-Julius</pre></div=
></div>

--047d7b6da18ad13458050cf2472f--


From nobody Tue Jan 20 14:36:46 2015
Return-Path: <juliusfriedman@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8557E1A0056; Tue, 20 Jan 2015 14:36:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7sYT5hJHd_4k; Tue, 20 Jan 2015 14:36:40 -0800 (PST)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CA2B1A005C; Tue, 20 Jan 2015 14:36:40 -0800 (PST)
Received: by mail-pa0-f48.google.com with SMTP id rd3so48546758pab.7; Tue, 20 Jan 2015 14:36:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=XyXh0cz2N08nDBkOFNXO9jnSOIlVvRzKljAE2daTLmQ=; b=w3dFCSoCLCvT54XEUmvAdaIe49JwTAY8aWzi+ekmaraXio3YnFqGqURDHelGAnfU6/ oSAGokVooTScAulBRgxuH2XblJSxd9cri3P1JvudUVn/mYvEWmNHGNnd5NwkL2ssocMa kIgwspXFK0KBFJ1TWIiGd+c9Um7y+X8/xLvFYVDzxRYxLbo0LqttFvQ/7jOmRZVp5zSs RHkkoqbt2C/ssKgT74OZIA6x1UnyIdmgsrA2lAmSIQJ9zYP69K4HRmwDlXtklfsORXkb AJJwqMeKCdJ7mbA1855P+B6QIrag4K9RIVQ2VyXn8iMaUh0HAEFrNei/QiW5lPUs2ycI /AVg==
MIME-Version: 1.0
X-Received: by 10.68.236.67 with SMTP id us3mr56002869pbc.121.1421793399616; Tue, 20 Jan 2015 14:36:39 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Tue, 20 Jan 2015 14:36:39 -0800 (PST)
In-Reply-To: <786615F3A85DF44AA2A76164A71FE1AC3871E2@FR711WXCHMBA03.zeu.alcatel-lucent.com>
References: <CACFvNHVFUe7jHEK00ja3Vppi5GYeKptOuVPi97HrYU3DdiyLCA@mail.gmail.com> <786615F3A85DF44AA2A76164A71FE1AC3871E2@FR711WXCHMBA03.zeu.alcatel-lucent.com>
Date: Tue, 20 Jan 2015 17:36:39 -0500
Message-ID: <CACFvNHXgPoV=p=q7R+9fMYHxcvAXKR6iEQ1G50aEYijqA7NwJA@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org, mmusic@ietf.org
Content-Type: multipart/alternative; boundary=047d7b2e11b1873add050d1d1227
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/DvHSI5SxJ0B_ZktqwV-ajIAHJVk>
Subject: Re: [AVTCORE] On RFC2326
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 22:36:44 -0000

--047d7b2e11b1873add050d1d1227
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks, at least I know that my emails are being receiving and that I am
being mostly ignored for whatever reason.

I appreciate the little time the committee has given me thus far and all I
can really say is 'Thank you'

It's a shame that one can so quickly be turned away from something which
they have been in support of for so long and in my opinion an unfortunate
reflection of the times and how this committee has failed to adapt to such.

It should be easy to communicate to the committee and if this list is a
hassle for those members than an alternate form of `communicae` should be
presented such that EVERYONE (who's RIGHT) it is to both utilize and
provide important input on these standards in a way that allows for such
dialog to be opened, addressed and resolved in a more appealing and
beneficial manner.

I don't wish to play tug of war for attention or confer with individuals
who who wish to hide behind opinions and intentions in a subject where such
things have no purpose other than fragmentation of the standards which are
developed to prevent such.

Furthermore with all due respect it is the RIGHT of this committee to do so
especially when their documents define what is 'correct' and 'incorrect'
AND more so when it provides appendixes which are incorrect or interpreted
to be so.

Instead what you have displayed via your responses and lack thereof is just
the opposite of that which you ask from others who communicate with you,
why would I even waste any more time? I can easily write my own standard
and submit it for review when I see fit.

Quite frankly I believe that the `owness` is on the committee and it's
members to be able to address these issues based on the fact they they
voted and approved these documents which convey public information to
parties who utilize and RELY upon them to communicate in heterogeneous
networks where their conformance can effect application security and
implementation compatibility;especially in such cases where applications
claim conformance to such standards.

I did my homework, I made my inquiries and I was ignored.

When I was wrong about terminology or reference I deferred and did not
respond in any way other than to further explain the core issue with a
succinct explanation, which was only met with hostility for what I can only
assume is because it's apparent that this committee has lost it's ability
to address issues and take responsibility when required to do so.

I used to believe that membership existed to provide the most beneficial
technology to everyone and anyone, instead I can see that it's now a
cesspool which is used to create standards and update existing standards
where it is beneficial for whatever corporate interest require the control
of such information.

Your responses which tangent into response furthermore the lack of ability
to understand both the nature of the errors and their proposed resolution
also indicates this; quite simply you would rather argue about terminology
and formatting or punctuation and dismiss ideas you can't easily understand=
.

If your the world's leading experts then I suppose that makes me the
world's leading expertise seeker among quite a few other things until this
point...

If I can be of any further `service` to the committee or respond in any way
which can actually be beneficial to both the proper development of internet
standards as they are required then please let me know, otherwise `ceterus
paribus` you will probably only hear from me when I file erratum for that
which I am ignored for including but not limited to existing issues which
have been reported numerous times.

I am only doing my duty when filling such erratum and if the committee
would respond and settle any debate intelligently and accurately without
deferring to ambiguous possibilities about courses of action then one would
oblige to such. Quite simply I provided everything I needed to and I even
went further to address why certain 'new' standards were required when
their functionality was encompassed via possibly an implementation of
alternate interpretation of existing mechanisms in existing standards.

In fact, the only ones demanding anything are certain members here:

"Follow this process", "Don't address this", "This is why this IS needed"

When in almost all of the cases including my favorite "Rtp has worked for
the last 20 years" crap... it just goes to show you that you have become
unable to function in the most simply capacity.

What I am to come away with from this experience is simply that the
committee doesn't handle questions very well and that asking questions is
trolling and that regardless if your are right or not the committee will
ignore you and move to mask your input as spam.

I wish I would have been able to start over and write in differently but
then I remember, I tried this for months and I am only human and I have my
own constraints with time and energy I must meet them before helping
everyone else especially when I am met with such resistance for no apparent
reason.

I apologize for anything I may have done and gracefully bow out.


With all due respect,
Julius Richard Friedman

On Mon, Jan 19, 2015 at 3:12 AM, Schwarz, Albrecht (Albrecht) <
albrecht.schwarz@alcatel-lucent.com> wrote:

>  Don=E2=80=99t waste any time anymore on RFC 2326:
>
>
>
> =3D> IF, THEN argue against 2326bis:
>
> https://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40
>
> RTSP version 2.0 which obsoletes RTSP version 1.0 defined in RFC 2326
> <https://tools.ietf.org/html/rfc2326>.
>
>
>
>
>
>
>
> *From:* avt [mailto:avt-bounces@ietf.org] *On Behalf Of *Julius Friedman
> *Sent:* Sonntag, 18. Januar 2015 20:34
> *To:* mmusic@ietf.org; avt@ietf.org
> *Subject:* [AVTCORE] On RFC2326
>
>
>
> Unfortunately I have more information which I have found to be
> contradictory and possibly erratum.
>
>
>
> Quite Succinctly,
>
>
>
> "
>  10.7 <https://tools.ietf.org/html/rfc2326#section-10.7> TEARDOWN
>
>
>
>
>
>    The TEARDOWN request stops the stream delivery for the given URI,
>
>    freeing the resources associated with it. If the URI is the
>
>    presentation URI for this presentation, any RTSP session identifier
>
>    associated with the session is no longer valid. Unless all transport
>
>    parameters are defined by the session description, a SETUP request
>
>    has to be issued before the session can be played again.
>
> "
>
>
>
> However earlier in the document.
>
>
>
> "
>
> 10.4 <https://tools.ietf.org/html/rfc2326#section-10.4> SETUP ....
>
> The server generates session identifiers in response to SETUP
>
>    requests. If a SETUP request to a server includes a session
>
>    identifier, the server MUST bundle this setup request into the
>
>    existing session or return error "459 Aggregate Operation Not
>
>    Allowed" (see Section 11.3.10 <https://tools.ietf.org/html/rfc2326#sec=
tion-11.3.10>).
>
> "
>
>
>
> If a users obtains a session Id related to an aggregate controlled media =
and only one of the sub sessions received a "TEARDOWN" then the RFC makes t=
he server incorrectly remove the SessionId which is still being used for th=
e other sub-sessions.
>
>
>
>
>
> The draft doesn't do any better in making this clearer IMHO.
>
>
>
> Please advise,
>
>
>
> I will also probably be filling more errata unless I can be directed on h=
ow to properly convey the information without filling it.
>
>
>
> I hope all else is well as I STILL haven't heard back from anyone regardi=
ng both the clarifications I made. (Which is pretty ridiculous, it's been o=
ver 2 years I have been asking these questions almost)
>
>
>
> -Julius
>
>

--047d7b2e11b1873add050d1d1227
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks, at least I know that my emails are being receiving=
 and that I am being mostly ignored for whatever reason.<div><br></div><div=
>I appreciate the little time the committee has given me thus far and all I=
 can really say is &#39;Thank you&#39;</div><div><br></div><div>It&#39;s a =
shame that one can so quickly be turned away from something which they have=
 been in support of for so long and in my opinion an unfortunate reflection=
 of the times and how this committee has failed to adapt to such.</div><div=
><br></div><div>It should be easy to communicate to the committee and if th=
is list is a hassle for those members than an alternate form of `communicae=
` should be presented such that EVERYONE (who&#39;s RIGHT) it is to both ut=
ilize and provide important input on these standards in a way that allows f=
or such dialog to be opened, addressed and resolved in a more appealing and=
 beneficial manner.</div><div><br></div><div>I don&#39;t wish to play tug o=
f war for attention or confer with individuals who who wish to hide behind =
opinions and intentions in a subject where such things have no purpose othe=
r than fragmentation of the standards which are developed to prevent such.<=
/div><div><br></div><div>Furthermore with all due respect it is the RIGHT o=
f this committee to do so especially when their documents define what is &#=
39;correct&#39; and &#39;incorrect&#39; AND more so when it provides append=
ixes which are incorrect or interpreted to be so.</div><div><br></div><div>=
Instead what you have displayed via your responses and lack thereof is just=
 the opposite of that which you ask from others who communicate with you, w=
hy would I even waste any more time? I can easily write my own standard and=
 submit it for review when I see fit.</div><div><br></div><div>Quite frankl=
y I believe that the `owness` is on the committee and it&#39;s members to b=
e able to address these issues based on the fact they they voted and approv=
ed these documents which convey public information to parties who utilize a=
nd RELY upon them to communicate in heterogeneous networks where their conf=
ormance can effect application security and implementation compatibility;es=
pecially in such cases where applications claim conformance to such standar=
ds.</div><div><br></div><div>I did my homework, I made my inquiries and I w=
as ignored.</div><div><br></div><div>When I was wrong about terminology or =
reference I deferred and did not respond in any way other than to further e=
xplain the core issue with a succinct explanation, which was only met with =
hostility for what I can only assume is because it&#39;s apparent that this=
 committee has lost it&#39;s ability to address issues and take responsibil=
ity when required to do so.</div><div><br></div><div>I used to believe that=
 membership existed to provide the most beneficial technology to everyone a=
nd anyone, instead I can see that it&#39;s now a cesspool which is used to =
create standards and update existing standards where it is beneficial for w=
hatever corporate interest require the control of such information.</div><d=
iv><br></div><div>Your responses which tangent into response furthermore th=
e lack of ability to understand both the nature of the errors and their pro=
posed resolution also indicates this; quite simply you would rather argue a=
bout terminology and formatting or punctuation and dismiss ideas you can&#3=
9;t easily understand.</div><div><br></div><div>If your the world&#39;s lea=
ding experts then I suppose that makes me the world&#39;s leading expertise=
 seeker among quite a few other things until this point...</div><div><br></=
div><div>If I can be of any further `service` to the committee or respond i=
n any way which can actually be beneficial to both the proper development o=
f internet standards as they are required then please let me know, otherwis=
e `ceterus paribus` you will probably only hear from me when I file erratum=
 for that which I am ignored for including but not limited to existing issu=
es which have been reported numerous times.</div><div><br></div><div>I am o=
nly doing my duty when filling such erratum and if the committee would resp=
ond and settle any debate intelligently and accurately without deferring to=
 ambiguous possibilities about courses of action then one would oblige to s=
uch. Quite simply I provided everything I needed to and I even went further=
 to address why certain &#39;new&#39; standards were required when their fu=
nctionality was encompassed via possibly an implementation of alternate int=
erpretation of existing mechanisms in existing standards.</div><div><br></d=
iv><div>In fact, the only ones demanding anything are certain members here:=
</div><div><br></div><div>&quot;Follow this process&quot;, &quot;Don&#39;t =
address this&quot;, &quot;This is why this IS needed&quot;</div><div><br></=
div><div>When in almost all of the cases including my favorite &quot;Rtp ha=
s worked for the last 20 years&quot; crap... it just goes to show you that =
you have become unable to function in the most simply capacity.</div><div><=
br></div><div>What I am to come away with from this experience is simply th=
at the committee doesn&#39;t handle questions very well and that asking que=
stions is trolling and that regardless if your are right or not the committ=
ee will ignore you and move to mask your input as spam.</div><div><br></div=
><div>I wish I would have been able to start over and write in differently =
but then I remember, I tried this for months and I am only human and I have=
 my own constraints with time and energy I must meet them before helping ev=
eryone else especially when I am met with such resistance for no apparent r=
eason.</div><div><br></div><div>I apologize for anything I may have done an=
d gracefully bow out.</div><div><br></div><div><br></div><div>With all due =
respect,</div><div>Julius Richard Friedman</div></div><div class=3D"gmail_e=
xtra"><br><div class=3D"gmail_quote">On Mon, Jan 19, 2015 at 3:12 AM, Schwa=
rz, Albrecht (Albrecht) <span dir=3D"ltr">&lt;<a href=3D"mailto:albrecht.sc=
hwarz@alcatel-lucent.com" target=3D"_blank">albrecht.schwarz@alcatel-lucent=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Don=E2=80=99t waste any t=
ime anymore on RFC 2326:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=3D&gt; IF, THEN argue ag=
ainst 2326bis:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><a href=3D"https://tools.=
ietf.org/html/draft-ietf-mmusic-rfc2326bis-40" target=3D"_blank">https://to=
ols.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40</a><u></u><u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">RTSP version 2.0 which obsoletes RTSP version 1.0 defined =
in
<a href=3D"https://tools.ietf.org/html/rfc2326" target=3D"_blank">RFC 2326<=
/a>.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> avt [mailto:<a href=3D"mailto:avt-bounces@ietf.org" t=
arget=3D"_blank">avt-bounces@ietf.org</a>]
<b>On Behalf Of </b>Julius Friedman<br>
<b>Sent:</b> Sonntag, 18. Januar 2015 20:34<br>
<b>To:</b> <a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf=
.org</a>; <a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a=
><br>
<b>Subject:</b> [AVTCORE] On RFC2326<u></u><u></u></span></p>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Unfortunately I have more information which I have f=
ound to be contradictory and possibly erratum.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Quite Succinctly,<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;<u></u><u></u></p>
</div>
<div>
<h3><a name=3D"14b013fcfec3f1e0_section-10.7"></a><a href=3D"https://tools.=
ietf.org/html/rfc2326#section-10.7" target=3D"_blank"><span style=3D"font-s=
ize:12.0pt;font-family:&quot;Courier New&quot;;color:black;text-decoration:=
none">10.7</span></a><span style=3D"font-size:12.0pt;font-family:&quot;Cour=
ier New&quot;;color:black">
 TEARDOWN<u></u><u></u></span></h3>
<pre><span style=3D"font-size:12.0pt;color:black"><u></u>=C2=A0<u></u></spa=
n></pre>
<pre><span style=3D"font-size:12.0pt;color:black"><u></u>=C2=A0<u></u></spa=
n></pre>
<pre><span style=3D"font-size:12.0pt;color:black">=C2=A0=C2=A0 The TEARDOWN=
 request stops the stream delivery for the given URI,<u></u><u></u></span><=
/pre>
<pre><span style=3D"font-size:12.0pt;color:black">=C2=A0=C2=A0 freeing the =
resources associated with it. If the URI is the<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12.0pt;color:black">=C2=A0=C2=A0 presentation=
 URI for this presentation, any RTSP session identifier<u></u><u></u></span=
></pre>
<pre><span style=3D"font-size:12.0pt;color:black">=C2=A0=C2=A0 associated w=
ith the session is no longer valid. Unless all transport<u></u><u></u></spa=
n></pre>
<pre><span style=3D"font-size:12.0pt;color:black">=C2=A0=C2=A0 parameters a=
re defined by the session description, a SETUP request<u></u><u></u></span>=
</pre>
<pre><span style=3D"font-size:12.0pt;color:black">=C2=A0=C2=A0 has to be is=
sued before the session can be played again.<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12.0pt;color:black">&quot;<u></u><u></u></spa=
n></pre>
<pre><span style=3D"font-size:12.0pt;color:black"><u></u>=C2=A0<u></u></spa=
n></pre>
<pre><span style=3D"font-size:12.0pt;font-family:&quot;Arial&quot;,&quot;sa=
ns-serif&quot;;color:#222222">However earlier in the document.</span><span =
style=3D"font-size:12.0pt;color:black"><u></u><u></u></span></pre>
<pre><span style=3D"font-size:12.0pt;color:black"><u></u>=C2=A0<u></u></spa=
n></pre>
<pre><span style=3D"font-size:12.0pt;font-family:&quot;Arial&quot;,&quot;sa=
ns-serif&quot;;color:#222222">&quot;</span><span style=3D"font-size:12.0pt;=
color:black"><u></u><u></u></span></pre>
<h3><a name=3D"14b013fcfec3f1e0_section-10.4"></a><a href=3D"https://tools.=
ietf.org/html/rfc2326#section-10.4" target=3D"_blank"><span style=3D"font-s=
ize:12.0pt;font-family:&quot;Courier New&quot;;color:black;text-decoration:=
none">10.4</span></a><span style=3D"font-size:12.0pt;font-family:&quot;Cour=
ier New&quot;;color:black">
 SETUP<u></u><u></u></span></h3>
<h3><span style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;;col=
or:black">....<u></u><u></u></span></h3>
<h3><span style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;;col=
or:black"><u></u>=C2=A0<u></u></span></h3>
<pre><span style=3D"font-size:12.0pt;color:black">The server generates sess=
ion identifiers in response to SETUP<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12.0pt;color:black">=C2=A0=C2=A0 requests. If=
 a SETUP request to a server includes a session<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12.0pt;color:black">=C2=A0=C2=A0 identifier, =
the server MUST bundle this setup request into the<u></u><u></u></span></pr=
e>
<pre><span style=3D"font-size:12.0pt;color:black">=C2=A0=C2=A0 existing ses=
sion or return error &quot;459 Aggregate Operation Not<u></u><u></u></span>=
</pre>
<pre><span style=3D"font-size:12.0pt;color:black">=C2=A0=C2=A0 Allowed&quot=
; (see <a href=3D"https://tools.ietf.org/html/rfc2326#section-11.3.10" targ=
et=3D"_blank">Section 11.3.10</a>).<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12.0pt;font-family:&quot;Arial&quot;,&quot;sa=
ns-serif&quot;;color:#222222">&quot;</span><span style=3D"font-size:12.0pt;=
color:black"><u></u><u></u></span></pre>
<pre><u></u>=C2=A0<u></u></pre>
<pre><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">I=
f a users obtains a session Id related to an aggregate controlled media and=
 only one of the sub sessions received a &quot;TEARDOWN&quot; then the RFC =
makes the server incorrectly remove the SessionId which is still being used=
 for the other sub-sessions.</span><u></u><u></u></pre>
<pre><u></u>=C2=A0<u></u></pre>
<pre><u></u>=C2=A0<u></u></pre>
<pre>The draft doesn&#39;t do any better in making this clearer IMHO.<u></u=
><u></u></pre>
<pre><u></u>=C2=A0<u></u></pre>
<pre>Please advise,<u></u><u></u></pre>
<pre><u></u>=C2=A0<u></u></pre>
<pre>I will also probably be filling more errata unless I can be directed o=
n how to properly convey the information without filling it.<u></u><u></u><=
/pre>
<pre><u></u>=C2=A0<u></u></pre>
<pre>I hope all else is well as I STILL haven&#39;t heard back from anyone =
regarding both the clarifications I made. (Which is pretty ridiculous, it&#=
39;s been over 2 years I have been asking these questions almost)<u></u><u>=
</u></pre>
<pre><u></u>=C2=A0<u></u></pre>
<pre>-Julius<u></u><u></u></pre>
</div>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--047d7b2e11b1873add050d1d1227--


From nobody Mon Jan 26 01:50:10 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23FF71A8856; Mon, 26 Jan 2015 01:50:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vn1R6A7QKZTA; Mon, 26 Jan 2015 01:50:04 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E0EF1A8880; Mon, 26 Jan 2015 01:50:03 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-0d-54c60dc96ba7
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id F9.9B.24955.9CD06C45; Mon, 26 Jan 2015 10:50:01 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.83) with Microsoft SMTP Server id 14.3.195.1; Mon, 26 Jan 2015 10:50:00 +0100
Message-ID: <54C60DC5.4090102@ericsson.com>
Date: Mon, 26 Jan 2015 10:49:57 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Dale R. Worley" <worley@ariadne.com>
References: <87vbkjd7yd.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87vbkjd7yd.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUyM+Jvje5J3mMhBtP3iFu87FnJbnH8RBOz xdTlj1ksXp4oc2DxmLz/K7PHzll32T2WLPnJFMAcxWWTkpqTWZZapG+XwJXRsqKTpaBFqGLq sidsDYzL+LoYOTkkBEwkzh47xQZhi0lcuLceyObiEBI4wiix42wDE4SznFFi/bFLTCBVvALa En9OPmQHsVkEVCU+rbvECGKzCVhI3PzRCDZJVCBYYvHzp6wQ9YISJ2c+Yeli5OAQEdCU6FiQ AxJmFnCU+PejD2yksIC+RP/cO8wgtpCAkcSElttgYzgFjCX29zaxQtQbSBxZNAfKlpdo3job ql5boqGpg3UCo+AsJNtmIWmZhaRlASPzKkbR4tTipNx0I2O91KLM5OLi/Dy9vNSSTYzAUD64 5bfqDsbLbxwPMQpwMCrx8G5cezREiDWxrLgy9xCjNAeLkjivnfGhECGB9MSS1OzU1ILUovii 0pzU4kOMTBycUg2MUZ3H/AqqXrmXTHB1Cf0/VT/o3o/vFnu/e8n8Vv6vtlp4Qu1KhiS+6JS/ 2vO6vrft+WIbtFrqw/LIdAPV9S2Rdqtatl5d2NClOSlI/sKRZpWIa765Va/5Yx+Jzc14Wuck VB+braJjrmoZ2nOoq/fKw71bD236lBS99+Frxd3uVdKfjga9nbhMiaU4I9FQi7moOBEAiMJY I0YCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/HEjihtU9CPeY1AyjEPtRHUq3sTk>
Cc: juliusfriedman@gmail.com, avt@ietf.org, mmusic@ietf.org
Subject: Re: [AVTCORE] Erratum 4097 on RFC 2435
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 09:50:06 -0000

Hi,

I don't see any change to the actual text. The note part appears to be
suggestion for a non-backwards compatible change. As said before,
technical modifications to specifications are not done using the Errata
system. Instead one will have to write a new specification (Internet
Draft) that is taken through the WG and IESG approval.

As this is non-backwards compatible change, I think the most likely
outcome would be to use a new RTP payload identifier for this new format.

Please note that the correct WG for RTP Payload specification work is
the PAYLOAD WG.

My suggestion is that this errata is rejected.

Cheers

Magnus


On 2015-01-06 20:28, Dale R. Worley wrote:
> I've looked at this erratum
> (http://www.rfc-editor.org/errata_search.php?eid=4097) and I don't think
> I understand it.
> 
> It contains a section titled "Section 3.1.5 says" and a section titled
> "It should say", but the bodies of the two sections are exactly the
> same.  (I used a text editor to compare them.)  So what change is
> described by the erratum?
> 
> There is a section titled "Notes" which says:
> 
>     Use a divisor of 256 to determine the height, where 8 / 256 = 32.
> 
>     Ensure FragmentOffset does not exceed 2^24, if it does then use 2^24
>     - value)
> 
> The first line does not seem to describe the computation described in
> the RFC text, and the equation in that line is incorrect.  (Was it
> supposed to be 256 / 8 = 32?)
> 
> The second line seems to be entirely unrelated to the rest of the
> erratum.  Perhaps it belongs in another erratum?  It also contains an
> unmatched ")".
> 
> Dale
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Mon Jan 26 04:23:04 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 340BD1A8968 for <avt@ietfa.amsl.com>; Mon, 26 Jan 2015 04:23:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qUo-F8eMeNAa for <avt@ietfa.amsl.com>; Mon, 26 Jan 2015 04:23:01 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1ACB81A89FA for <avt@ietf.org>; Mon, 26 Jan 2015 04:23:00 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-b2-54c631a3247d
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id C6.94.24955.3A136C45; Mon, 26 Jan 2015 13:22:59 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.80) with Microsoft SMTP Server id 14.3.195.1; Mon, 26 Jan 2015 13:22:58 +0100
Message-ID: <54C6319E.4040708@ericsson.com>
Date: Mon, 26 Jan 2015 13:22:54 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Julius Friedman <juliusfriedman@gmail.com>, Roni Even <ron.even.tlv@gmail.com>, <avt@ietf.org>
References: <20141204014737.6282D181CD3@rfc-editor.org> <038501d01a0c$93470820$b9d51860$@gmail.com> <CACFvNHWWUGTPLkQuv=6NJuzptA6kNa504JexGOnfL6cqLL7YXQ@mail.gmail.com>
In-Reply-To: <CACFvNHWWUGTPLkQuv=6NJuzptA6kNa504JexGOnfL6cqLL7YXQ@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHLMWRmVeSWpSXmKPExsUyM+Jvje5iw2MhBh9nSVi87FnJbnH8RBOz xd92Zgdmj52z7rJ7LFnykymAKYrLJiU1J7MstUjfLoEr40LTIeaC+0oVOze/ZW9g/CbdxcjJ ISFgIvHr5WImCFtM4sK99WwgtpDAEUaJ1y8Cuxi5gOzljBJ3Tu9kBknwCmhLzH5xnh3EZhFQ lXj9cyYriM0mYCFx80cjWLOoQLDE4udPWSHqBSVOznzCAmKLCKRILJo9G2yOsICjxOKlLxkh FqxglJjXuhmsmVMgUGLqt3VgDcwCBhJHFs1hhbDlJZq3QjQLAR3R0NTBOoFRYBaSHbOQtMxC 0rKAkXkVo2hxanFSbrqRsV5qUWZycXF+nl5easkmRmCAHtzyW3UH4+U3jocYBTgYlXh4N649 GiLEmlhWXJl7iFGag0VJnNfO+FCIkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBkZGxRL23C8z 9/Z3xqceZDGeaDUrkrPSfZJ1allg8KGkj9EXNwsssVQS5H2oW1bxTkdKTjb1rfr+oN+Wigc+ NHb/irxXW9DLGPRiwuvICBuWfFNxUXaNqSvKlq1Y35wgHHGC++rh4LubDU9uf3z6+NPbq0Mk A7JXyT1qklqxbm514pbQJ5u9lymxFGckGmoxFxUnAgCFi7laMQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/n0xissV8TkqXwFpGXCMtqt7DMjs>
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC3550 (4192)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 12:23:03 -0000

Hi Julius

On 2014-12-17 16:36, Julius Friedman wrote:
> So quite simply how can jitter and transit use the absolute time from
> packet to packet but yet the calculation of payload data rate is using
> the same?
> 
> Wouldn't time spent on non data items be used then?

I don't quite understand you here. But, I guess that you are complaining
about that the measured entity is not the most relevant.

However, this is not at all reason enough to make a change to the RTCP
report block specification in RFC 3550. As noted before, using Errata is
not the appropriate method for technical change. Errata is used to flag
significant issues, or clarify text that might be misinterpret to avoid
incompatibility issue.

> 
> What about the security concerns related to congruence?

If I understand the security concern correctly. This is that in case one
uses padded payloads in the protection operation, this report leaks the
summary over the amount of new payload bytes received between each
report, potentially for a single packet. Thus providing an information
leak that might provide some insight into the protected data. For
example the audio frame lengths from a variable rate codec.

In would agree that this would be worth taking note of as a security
issue. Potentially change the design to avoid it. However, I would first
of all note that this RTCP definition has been in place since 1996. It
is very widely deployed and any change to it would result in
incompatibilities.

Further it is clearly possible to protected against. Simply encrypt the
RTCP also. Which would be my recommendation anyway if one encrypts the
RTP packets.

> 
> How is that not errata unless these invalid calculations and security
> issues were intentionally mandated and why now would I knowing these
> things continue to do things as usual?

First of all it is a technical change that is non-backwards compatible.
It does not represent clarifying the WG consensus on how it should be done.

> 
> Furthermore can you simply tell me what breaks if I use the octets
> indicated as I indicated (by only not accounting for the 12 octet header)?

Any implementation that tracks these values would flag an inconsistency
and possible cease transmission. Because your receiver will claim to
have received more bytes than the sending party has sent according to
its calculation of this value.

> 
> WITH ALL DUE RESPECT That should be the determining factor not your
> opinions about intentions.

Please understand a few things. There are process that exist. There are
purposes and rules for what is allowed to be done with difference
processed and mechanisms. In addition there are considerations of the
impact of any changes to existing specifications. Which in its turn
leads back to the process question.

Roni, in his role a WG co-chair has the responsibility for driving these
processes. One of these is to determine the WG's recommendation to the
AD for how an errata is to be handled.

> 
> My tests reveal faster synchronization with rtcp with legacy clients as
> well as a correct rate and data rate when then is calculated by removing
> the csrc extension and padding.

Sorry, I don't understand how you get faster synchronization. This
should have no effect on the RTCP packet transmission rules and their
execution.

> 
> How about some calculations and tests are also performed to validate
> this as most default profiles don't use any of the items in question
> anyway.


> 
> Additionally why has nothing been said about rfc2326 and errata 4199?
> 

RFC 2326 is an MMUSIC item. Please, keep the topics separated and with
clear subject lines. Please avoid cross posting between the WG mailing
lists.

Can you please refrain from creating more erratas until you have
achieved some WG consensus that any issue is requiring an errata and
what the new text should actually be.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Mon Jan 26 04:35:56 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 158961A8A59 for <avt@ietfa.amsl.com>; Mon, 26 Jan 2015 04:35:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_SUMOF=1, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vn_YTqWna9_y for <avt@ietfa.amsl.com>; Mon, 26 Jan 2015 04:35:52 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DC161A8A06 for <avt@ietf.org>; Mon, 26 Jan 2015 04:35:51 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-cb-54c634a58d00
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id A3.96.24955.5A436C45; Mon, 26 Jan 2015 13:35:49 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.41) with Microsoft SMTP Server id 14.3.195.1; Mon, 26 Jan 2015 13:35:49 +0100
Message-ID: <54C634A0.5080302@ericsson.com>
Date: Mon, 26 Jan 2015 13:35:44 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Harald Radke <harryrat@gmx.de>, <avt@ietf.org>
References: <trinity-db1651cc-9514-495d-b11b-281dc69b056c-1420467617692@3capp-gmx-bs11>
In-Reply-To: <trinity-db1651cc-9514-495d-b11b-281dc69b056c-1420467617692@3capp-gmx-bs11>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCLMWRmVeSWpSXmKPExsUyM+Jvje5Sk2MhBnO2mFu87FnJbvHup7gD k8eHj3EeS5b8ZApgiuKySUnNySxLLdK3S+DKePr7HVPBS+mKv19XMDcwbhLrYuTgkBAwkWjZ GtjFyAlkiklcuLeeDcQWEjjCKDFvvkAXIxeQvZxR4s/vaWwg9bwC2hLd7QogNSwCqhIb5n5l BLHZBCwkbv5oBOsVFQiWWPz8KSuIzSsgKHFy5hMWEFtEwEhicsMsZhBbWMBcYtbeJrCRQgLh Evd/SoKEOQUiJA5dXQBWzixgIHFk0RxWCFteonnrbGaI07QlGpo6WCcwCsxCsmEWkpZZSFoW MDKvYhQtTi1Oyk03MtZLLcpMLi7Oz9PLSy3ZxAgMxoNbfqvuYLz8xvEQowAHoxIP78a1R0OE WBPLiitzDzFKc7AoifPaGR8KERJITyxJzU5NLUgtii8qzUktPsTIxMEp1cDY/z13aUB+fZbL lda3E5ZEZXlM5EyKfpX2bcevTgXTcNc3MTq6D6Mq8qV/6hvuXP73J+eKVm2+uUclme9VGbGl 95a+uLzyZdgTy1k3Ti3I3LW25IfrzW9Cz1d3ijrWHnuiestdTEMnYG3A0d5VGdONXeyiXxq+ T/5aPmWvaPWMhVvX5UydM/G5EktxRqKhFnNRcSIA3ZfzwycCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/mM7HYRc6NA6JAnzDK0aLGPl8aT8>
Subject: Re: [AVTCORE] RFC4566 - understanding maxptime
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 12:35:54 -0000

Hi,

I think I can provide some explanation as the one that actually wrote
this originally

On 2015-01-05 15:20, Harald Radke wrote:
> Hi all,
>  
> I have slight troubles to understand the RFC4566 definition of the
> maxptime attribute
>  
> (if this mailing list is not the right place to ask questions to
> understand RFCs, just to discuss them, I  am sorry, just tell me and I
> wont bother you any further).
>  
> RFC4566 states:
>  
> a=maxptime:<maximum packet time>
> This gives the maximum amount of media that can be encapsulated
> in each packet, expressed as time in milliseconds. The time
> SHALL be calculated as the sum of the time the media present in
> the packet represents. [...]
>  
> 1) I kinda get the first sentence, but what does that second sentence
> actually mean? I kinda have problems understanding the SUM
> statement. Does that "only" mean that in case of multiple frames in one
> packet that all frame durations are summed up? I wonder because the
> ptime definition does not contain a similar statement.

The second part is there to deal with the cases when an RTP payload
contains multiple frames, for example AMR frames that has a duration of
20 ms. But, as the AMR RTP payload format supports Interleaving also,
the maxptime is the amount of audio frames actually contained in payload
rather than the duration between the oldest and newest media present. So
maxptime=100 allows for 5 AMR audio frames, independent of how far
between they are interleaved.

>  
> 2) Actually somebody already asked a similar question some time
> (actually years) ago, actually the difference between ptime and
> maxptime, the answer was:
>  
>>The "a=ptime:" attribute is a hint to the encoder on the preferred
> packetisation interval for the media. The encoder may follow the hint,
> or it may vary the packetisation >interval up to the value indicated by
> "a=maxptime:". The receiver is expected to be able to decode any
> reasonable packetisation.
>  
> a)is the receiver expected to decode ANY packetisation? (e.g. ptime=20,
> maxptime=40 -> incoming RTP packets of the stream might contain payloads
> worth of any length between 20 and 40ms, in case of sample based codecs
> with sample duration granularity?)

With the most liberal interpretation the answer is yes. But, in practice
I think reasonable number of samples is expected. Unfortunately there
are no defined list of these lengths to my knowledge.

>  
> b) must the receiver be able to handle varying packetisation during a
> session? that is receiving RTP packets with different payload lengths
> and different interarrival times or does "vary" just mean  that the
> sender "selects" one packetisation interval between ptime and maxptime
> at the beginningbut keeps it constant during the session?

Yes, the amount of media in the different RTP payloads are expected to
be changed during the RTP session. This to deal with changing latency,
available bandwidth and other changes during the duration of the session.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Mon Jan 26 05:00:18 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42F231A8A84 for <avt@ietfa.amsl.com>; Mon, 26 Jan 2015 05:00:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jF78WrLpvHvG for <avt@ietfa.amsl.com>; Mon, 26 Jan 2015 05:00:02 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E85E1A8A60 for <avt@ietf.org>; Mon, 26 Jan 2015 05:00:01 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-31-54c63a4fb077
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id C3.0A.24955.F4A36C45; Mon, 26 Jan 2015 13:59:59 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.59) with Microsoft SMTP Server id 14.3.195.1; Mon, 26 Jan 2015 13:59:59 +0100
Message-ID: <54C63A4B.4070708@ericsson.com>
Date: Mon, 26 Jan 2015 13:59:55 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Julius Friedman <juliusfriedman@gmail.com>, Simon Perreault <sperreault@jive.com>, <avt@ietf.org>
References: <CACFvNHXjy+PxHaZsrjdO5SHg6PSaQVt_J8WPH6hQTKQKkdoo5A@mail.gmail.com> <877fxy6s9u.fsf@hobgoblin.ariadne.com> <CACFvNHWW-HFWVPT2R04ywA9_vz6KkR+7SKC3BEiXDG0rWKN=ZQ@mail.gmail.com> <CANO7kWC=3tRYHMuZp3NY9ZNQFAsur7me6xVCZiT6RGzJMm+Rdw@mail.gmail.com> <CACFvNHVpNnk8939AVmU-mFVMSqGGo0pZ0y4T=7V58DGD9VYG5g@mail.gmail.com>
In-Reply-To: <CACFvNHVpNnk8939AVmU-mFVMSqGGo0pZ0y4T=7V58DGD9VYG5g@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUyM+Jvja6/1bEQg3WNZhYve1ayWxw/0cRs cf1KqAOzx85Zd9k9liz5yeTxb85T5gDmKC6blNSczLLUIn27BK6MXVv+MhecEK+4+egTSwPj BaEuRk4OCQETif7tE1kgbDGJC/fWs3UxcnEICRxhlOjZtZAVwlnOKDFxTS8bSBWvgLbE62s/ wGwWAVWJtzPeM4PYbAIWEjd/NILFRQWCJRY/f8oKUS8ocXLmE7ANIgLpEt+uzQCrFwaa8+p1 MwvEgmNMEi0HfzCCJDgFAiUu93YxgdjMAgYSRxbNYYWw5SWat84GaxYCam5o6mCdwCgwC8mO WUhaZiFpWcDIvIpRtDi1OCk33chYL7UoM7m4OD9PLy+1ZBMjMFgPbvmtuoPx8hvHQ4wCHIxK PLwb1x4NEWJNLCuuzD3EKM3BoiTOa2d8KERIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QDIxtD fuynh4/+HU2dpumkKvyzwspqY9z3g3sle4QvXPBQ9o85Mzfxw9LKqdcmVyzeebx/X4rQEn7l 3V2TSld+LNfov1j88WXc4ew9s9dcMfVo/bDwwLbnQjtbmB9sysqa93HdTvXzt0ynuuzSeaX5 o7L2wNWCXzP7RWfdv/XBTGjFwq02e3LjWdmUWIozEg21mIuKEwHO7s7JNwIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/GCZkxgWlT8RVCA6ew84agoRpu0Q>
Subject: Re: [AVTCORE] Errata 4192 RFC 3550
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 13:00:10 -0000

Hi Julius,

One more mail on your argumentation on why this needs any change at all.

It appear to me that you consider it wrong for a sender or receiver to
report different things with different definitions. So the Sender's
octet count reports on how many bytes the sender has included in the RTP
payload part of the RTP packet. While any timestamping in RTP is
attempted to be done on the RTP packet as whole unit, not specifically
the boundary of the payload for example.

In general the implementation is expected to do its best to timestamp
packets both on sending and receiving. But, unless special
implementations are deployed, these will be done either a bit prior to
any transmission onto a actual physical medium and after on reception.
In most cases this error may be significant because implementations does
not see packets until they come out of the used network API.

cheers

Magnus

On 2014-12-11 19:10, Julius Friedman wrote:
> So then are you implying that it would be correct to change the
> definition of timestamp and other such proposed changes while not
> allowing this one?
> 
> Have I not show that it is incorrect to take the transit time including
> the header but then send only the "payload" count in the report?
> 
> Even when the definition and calulcations just explicitly given show
> that the times taken include ANY data transfer including non rtp?
> 
> Making the change in text makes this calulcations correct and
> unambiguous just as the other proposed changes which are being
> contemplated.
> 
> It also allows for more than correctness by showing when a route is
> altered.
> 
> What reason is there to acknowledge this but reject the errata only to
> propose a new draft?
> 
> On Dec 11, 2014 12:30 PM, "Simon Perreault" <sperreault@jive.com
> <mailto:sperreault@jive.com>> wrote:
> 
> 
>     On Thu, Dec 11, 2014 at 10:20 AM, Julius Friedman
>     <juliusfriedman@gmail.com <mailto:juliusfriedman@gmail.com>> wrote:
> 
>         How can the items be excellent for a draft but not consideration
>         for errata?
> 
> 
>     Errata is appropriate when an RFC doesn't reflect what the working
>     group meant.
>     A draft is appropriate when an RFC does reflect what the working
>     group meant, but the working group was wrong.
> 
>     Simon
> 
> 
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Tue Jan 27 05:41:09 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DCA91A026F; Tue, 27 Jan 2015 05:41:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jAKkqq4kH7ql; Tue, 27 Jan 2015 05:40:59 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 045021A1A6E; Tue, 27 Jan 2015 05:40:57 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-d1-54c79567cdef
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id CC.E5.04231.76597C45; Tue, 27 Jan 2015 14:40:56 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.56) with Microsoft SMTP Server id 14.3.195.1; Tue, 27 Jan 2015 14:40:51 +0100
Message-ID: <54C79563.2040006@ericsson.com>
Date: Tue, 27 Jan 2015 14:40:51 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Julius Friedman <juliusfriedman@gmail.com>, <mmusic@ietf.org>, <avt@ietf.org>
References: <CACFvNHUz=VfYj+nz_WXbEvmzGvmNUiocCM1doPoPNJH+Qsemow@mail.gmail.com> <87a924c1xl.fsf@hobgoblin.ariadne.com> <CACFvNHXo4Jdmb9tsP-Yyoy3PAhLYO4_ubN4BoC4mDpgFYv_boQ@mail.gmail.com> <CACFvNHW9fr2ykT7tsGwCg8+k-JuxRPQVaLVK2sVdsdb_MFFeZw@mail.gmail.com> <CACFvNHVyhvd5MJi3mYL-4A4jTu2UTjmFwtORDx_mnV_TjGvirw@mail.gmail.com>
In-Reply-To: <CACFvNHVyhvd5MJi3mYL-4A4jTu2UTjmFwtORDx_mnV_TjGvirw@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrILMWRmVeSWpSXmKPExsUyM+JvjW7G1OMhBlMXc1m87FnJbnH8RBOz xdTlj1kcmD12zrrL7rFkyU+mAKYoLpuU1JzMstQifbsErozNu54wFux6xVhx4PB0lgbGN+sZ uxg5OSQETCRa5/1nh7DFJC7cW8/WxcjFISRwhFFi7uGFLBDOckaJ80tuMYFU8QpoS/x/P4sZ xGYRUJX42r8KbBKbgIXEzR+NbCC2qECwxOLnT1kh6gUlTs58AjSIg0MEKL7kRxxIWFggSOLt 07uMEPOPMUksv7gabCanQKBE642FYBcxCxhIHFk0hxXClpdo3jobrEYI6IaGpg7WCYwCs5Cs mIWkZRaSlgWMzKsYRYtTi4tz042M9VKLMpOLi/Pz9PJSSzYxAsP04JbfujsYV792PMQowMGo xMNr8P9YiBBrYllxZe4hRmkOFiVxXjvjQyFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGMtM FVpXdWyRMakRTuX919D+okDYNeJ1iHpcXEsOv0d7aIPvCqUfR44qbwyy/SVZ5ywQfe7/YqGK Pe6Pmt49DFZpWKSsdC7n0uw3Bb8/Si6bpsftai1dPSleJqhdXC7sVIjJzduGVodzPxqoCEn0 XAoN79mQ9m+R2xn9g7tYDkyJe3Htdeh0JZbijERDLeai4kQAPinDUTQCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/ejS04Fk8-H8DcwYvdO0F2NdAahk>
Subject: Re: [AVTCORE] Possible Erratta in RFC2326 relating to 'source' parameter.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jan 2015 13:41:05 -0000

Hi Julius,

the Source parameter is the source address of the RTP media stream. When
using RTCP it will also be the source address for RTCP. So, this
information should not be provided in a C->S Setup request. Only in the
S->C response when we are doing playback. As it is the servers address
from where it will send the media.

For RTP over UDP there is no way of knowing that the client does this
correctly and that the media path(s) are correctly established unless
the solution for NAT traversal in
https://datatracker.ietf.org/doc/draft-ietf-mmusic-rtsp-nat/ is used.
Which do verify that there are RTSP agents with the agreed on
credentials at the peer end of the media paths.

I hope this answers your questions. If not can you provide more focused
questions.

Cheers

Magnus

On 2015-01-04 21:47, Julius Friedman wrote:
> Please find my previous message without the attachment which seems to
> have been the result of why it was not received.
> 
> --------------------
> 
> I have come across several entities which use the 'source' datum but it
> usually contains their own [IP] Address, I am not sure why giving
> another [IP] Address there would be useful since it would probably be
> routed anyway.
> 
> I just wanted to make sure I wasn't missing anything and you came up
> with a perfect answer so, Thank you !
> 
> I would like to also point out that it also is a security concern
> because it can allow a client to connect to another server and this just
> looks like part of the RTSP negotiation; 
> 
> I can then technically also use any Rtsp server to DOS another server by
> having it attempt to connect to that server to setup something repeatedly. 
> 
> Additionally the server @ 'source' has no way of knowing the client
> would even be connecting to it and the client may not even be allowed to.
> 
> This is the text verbatim:
> 
>    source:
>           If the source address for the stream is different than can be
>           derived from the RTSP endpoint address (the server in playback
>           or the client in recording), the source MAY be specified.
> 
> The SDP has been exchanged and would then contain the necessary information about connection information, the source is the 'EndPoint' [IP] Address / Port pair from which the 'Request' has been received, taking any other such notion of this would not be beneficial in any circumstance, including `proxying` because the proxy would handle 'EndPoint' negotiation and have it's own set of headers to support such.
> 
> Based on these concerns can `source` be amended to indicate it's only such and not defined for use in the 'RTP/AVP' profile?
> 
> It would also reduce some of the work in the latest draft which indicate concerns about this parameter.
> 
> .Since we are on the subject of the 'Transport' header I have another question 'ssrc' in the same parameter, I have written into the 'mmusic' group several times but for some reason they don't seem to be responding.
> 
> Can a client send his 'ssrc' to the server? 
>  - (Obviously he can but) Is this already legal with the current spec? 
>  - If so how can the server distinguish it's own `ssrc` in the response?
> (E.g. if the server doesn't want that client to use that `ssrc` for some
> reason)
> 
> Why would this need to be done? in situations where a client is joining
> a session where many participants may already be active (especially
> multicast) it would be beneficial to avoid early 'ssrc' collisions with
> one of those.
> 
> Yes the client can already do this by just waiting for the response to
> assign it's own `ssrc` but the response does not indicate the 'ssrc' of
> ALL participants only that of the media server, rtcp eventually sorts
> this out with a Goodbye and then a new ssrc but none the less I assume
> that saving that time and bandwidth and also having the option to assign
> both client and server ssrc would also have other benefits.
> 
> Moving back to the part about the peculiar punctuation.. I believe these
> peculiarities come from a notion that everything was text based.
> 
> The latest draft makes no changes at all to this besides defining more
> syntax.
> 
> Since the binary framing was apparently an after thought (based on
> information from the drafts which show interleaved data in a 'DATA' RTSP
> response) I think this was remnant from that in some way or at least
> that's the best I can possibly imagine.
> 
> Why the framing octet would also be listed as a 'safe' character is
> beyond me, there were several other characters / octets which definitely
> could have been used e.g. 0xC3 -> 0xFF.
> 
> The fact that the document makes so many statements about ease of
> parsing and then literally and figuratively destroy this concept with
> bad decisions such as the framing character as well as the interesting
> syntax for the markup.
> 
> I will past some of those here :
> 
> 
>       1.4 <https://tools.ietf.org/html/rfc2326#section-1.4> Protocol
>       Properties
> 
> 
> 
>    RTSP has the following properties:
> 
> ....
> 
>    Easy to parse:
>           RTSP can be parsed by standard HTTP or MIME parsers.
> 
> 
> 
> ...
> 
> 
> 
>     4 <https://tools.ietf.org/html/rfc2326#section-4> RTSP Message
> 
> 
> 
>    RTSP is a text-based protocol and uses the ISO 10646 character set in
>    UTF-8 encoding (RFC 2279 <https://tools.ietf.org/html/rfc2279> [21]). Lines are terminated by CRLF, but
>    receivers should be prepared to also interpret CR and LF by
>    themselves as line terminators.
> 
>      Text-based protocols make it easier to add optional parameters in a
>      self-describing manner. Since the number of parameters and the
>      frequency of commands is low, processing efficiency is not a
>      concern. Text-based protocols, if done carefully, also allow easy
>      implementation of research prototypes in scripting languages such
>      as Tcl, Visual Basic and Perl.
> 
>      The 10646 character set avoids tricky character set switching, but
>      is invisible to the application as long as US-ASCII is being used.
>      This is also the encoding used for RTCP. ISO 8859-1 translates
>      directly into Unicode with a high-order octet of zero. ISO 8859-1
>      characters with the most-significant bit set are represented as
>      1100001x 10xxxxxx. (See RFC 2279 <https://tools.ietf.org/html/rfc2279> [21])
> 
>    RTSP messages can be carried over any lower-layer transport protocol
>    that is 8-bit clean.
> 
>    Requests contain methods, the object the method is operating upon and
>    parameters to further describe the method. Methods are idempotent,
>    unless otherwise noted. Methods are also designed to require little
>    or no state maintenance at the media server.
> 
> 
> 
> This literally becomes a nightmare when you have to reconstruct TCP
> sequences.
> 
> I have attached a small 3MB zipped Wireshark capture which shows one
> such case of my dealing with this issue.
> 
> This is only exacerbated by the fact the document allows packets up to
> the maximum holding size in this mode AND specifies that packets with an
> unknown context must be skipped...
> 
> Skipped how? Skipped as in past their header, past their data? Can that
> text even be there?
> 
> We are talking about TCP and in such a case the data from a previous
> segment was already received by the receiver and contains only some of
> the data how would they skip data they have yet to receive? 
> 
> I will explain why this is a security issue, Since there is no sequence
> information in the binary header it must be trusted to contain valid
> length values. Without inspecting the latter octets one can make no such
> assumption about the type of binary data contained therein, especially
> if there is no context assigned.
> 
> This if I can get a single TCP packet into a stream I can very easily
> inject a lot of 'receive' space thus exponentially increasing my chances
> of getting another packet into the stream.
> 
> I think that there should at the very least be a correlation between
> 'Block-Size' and the frame size such that frame sizes MUST NOT ever be
> larger than that value if not already.
> 
> Furthermore I think that something needs to be done to specify how to
> deal with nuisances such as 'more / less bytes available than indicated
> in frame' especially when we also have 'Rtsp' messages which can be
> interleaved at the same time in between frames (which can contain "$").
> 
> So to re-iterate my understanding of how things are in toto I have an
> example I will outline below which is is a Rtsp Binary Interleaved
> sender who tells a Rtsp Binary Interleaved client there is a frame of
> 48344 bytes on channel 0.
> 
> The client received only 1328 bytes.
> 
> 47016 bytes remain.
> 
> The client starts to receive again.
> 
> At this point there should only be the rest of the data in the frame
> (47016 bytes)
> 
> This data will come over several MSS sized segments, during which time
> the socket may also be written to again (before the segment is
> transmitted to the client).
> 
> {
>     If the latter data happens to get to the receiver before the other
> portions of the segment we have TCP 're-ordering' based on the sequence
> number and may multiple ACK's for the early packets.
> 
>     If any data is missed we will have a re-transmission.
> 
>     The data being 'received' on the socket by the receiver coming from
> the server comes from the data portion of the tcp packet which now
> contains data from a previous segment.
> }
> 
> The sender is now committed to sending the additional bytes as indicated
> however if the sender stops sending this data or it's truncated it will
> never make to the receiver. The stack will never be able to re-assemble
> the packet and now framing sync is lost.
> 
> At this point ANY data consumed from the initial frame header and data
> which was received must ALSO be dis-guarded but there is NO WAY for the
> server to indicate this to the client... (This is why UDP is commonly
> used, you get what you get and you don't what you don't)
> 
> There are a lot of articles outlining why TCP and RTP don't get along
> mostly citing the overhead of re-transmissions so with Rtsp you think we
> would have attempted to solve this not make it worse with bad encapsulation.
> 
> Something needs to be done about this because it's also a security
> concern, e.g. if a client were to send a rtcp packet to the server which
> is very larger and contains no data he could attempt to exhaust the
> resources of that server (if they didn't monitor their rtcp bandwidth
> properly) or at least force a higher amount of traffic.
> 
> So, information needs to be clear that there is no such thing as a
> packet of less then 8 bytes under rtcp and 16 bytes under rtp. (Unless
> compression is being used; ROHC or otherwise)
> 
> The null packet or any packet under 16 bytes would used for 'spacing'
> not a 'unknown' context, especially when I can have 255 channels, what
> unknown context am I going to use then?
> 
> That is 4 octets for the `$` header, and the rest for the the packet
> header which can then be inspected to be the same version, payloadtype
> and ssrc as required by the client.
> 
> This prevents a client who may also send a "GET_PARAMETER" under
> interleaved transport with weird headers and a body to attempt underflow
> also which is something the current specification does nothing to
> protect against.
> 
> "GET_PARAMATER rtsp://someuri/ RTSP/1.0\r\nCSeq:1\r\nDate:
> xx:xx:xx\r\nContent-Length:24\r\n$UserAgent
> $009\r\n$\0\0\aRTSP/1.$\0\0\r\n\r\nDatawith$IsNotAGoodIdea!\0\0"
> 
> This would allow applications to still take note of when a large frame
> was seen but not be forced to act upon it and potentially lose data, and
> depending on their implementation allow remote code execution.
> 
> I urge the committee to seriously look into these issues as they can
> have a large impact.
> 
> https://isecpartners.github.io/fuzzing/vulnerabilities/2013/12/30/vlc-vulnerability.html
> 
> VLC seems protected against overflow after this but with some testing I
> have determined that not only VLC but other servers and clients are
> vulnerable to underflow this way as well making it both a server and
> client issue.
> 
> I have more notes in my implementation
> @ https://net7mma.codeplex.com/SourceControl/latest#Rtp/RtpClient.cs if
> your interested, it relates to one issue I saw where even though frame
> length was good other data in the packet was invalid such as the
> 'Extension' or the 'Length In Words Minus 1' or the ssrc etc.
> 
> Hopefully I didn't banter to much, it's rather late.
> 
> As for my other 'issues' / errata for RFC2435 has anything been
> determined on them?
> 
> What about the one for RFC3550, has anyone sat down to do the math on
> that one yet?
> 
> Thanks again for your time and response and have a Happy New Year if I
> don't hear back by then!
> 
> Sincerely,
> Julius Friedman
> 
> 
> On Sun, Jan 4, 2015 at 3:28 PM, Julius Friedman
> <juliusfriedman@gmail.com <mailto:juliusfriedman@gmail.com>> wrote:
> 
>     This is a re-transmission of my previous response which didn't seem
>     to make it to the list...
> 
>     Is there any way to confirm if I am properly signed up?
> 
>     I have come across several entities which use the 'source' datum but
>     it usually contains their own [IP] Address, I am not sure why giving
>     another [IP] Address there would be useful since it would probably
>     be routed anyway.
> 
>     I just wanted to make sure I wasn't missing anything and you came up
>     with a perfect answer so, Thank you !
> 
>     I would like to also point out that it also is a security concern
>     because it can allow a client to connect to another server and this
>     just looks like part of the RTSP negotiation; 
> 
>     I can then technically also use any Rtsp server to DOS another
>     server by having it attempt to connect to that server to setup
>     something repeatedly. 
> 
>     Additionally the server @ 'source' has no way of knowing the client
>     would even be connecting to it and the client may not even be
>     allowed to.
> 
>     This is the text verbatim:
> 
>        source:
>               If the source address for the stream is different than can be
>               derived from the RTSP endpoint address (the server in playback
>               or the client in recording), the source MAY be specified.
> 
>     The SDP has been exchanged and would then contain the necessary information about connection information, the source is the 'EndPoint' [IP] Address / Port pair from which the 'Request' has been received, taking any other such notion of this would not be beneficial in any circumstance, including `proxying` because the proxy would handle 'EndPoint' negotiation and have it's own set of headers to support such.
> 
>     Based on these concerns can `source` be amended to indicate it's only such and not defined for use in the 'RTP/AVP' profile?
> 
>     It would also reduce some of the work in the latest draft which indicate concerns about this parameter.
> 
>     .Since we are on the subject of the 'Transport' header I have another question 'ssrc' in the same parameter, I have written into the 'mmusic' group several times but for some reason they don't seem to be responding.
> 
>     Can a client send his 'ssrc' to the server? 
>      - (Obviously he can but) Is this already legal with the current spec? 
>      - If so how can the server distinguish it's own `ssrc` in the
>     response? (E.g. if the server doesn't want that client to use that
>     `ssrc` for some reason)
> 
>     Why would this need to be done? in situations where a client is
>     joining a session where many participants may already be active
>     (especially multicast) it would be beneficial to avoid early 'ssrc'
>     collisions with one of those.
> 
>     Yes the client can already do this by just waiting for the response
>     to assign it's own `ssrc` but the response does not indicate the
>     'ssrc' of ALL participants only that of the media server, rtcp
>     eventually sorts this out with a Goodbye and then a new ssrc but
>     none the less I assume that saving that time and bandwidth and also
>     having the option to assign both client and server ssrc would also
>     have other benefits.
> 
>     Moving back to the part about the peculiar punctuation.. I believe
>     these peculiarities come from a notion that everything was text based.
> 
>     The latest draft makes no changes at all to this besides defining
>     more syntax.
> 
>     Since the binary framing was apparently an after thought (based on
>     information from the drafts which show interleaved data in a 'DATA'
>     RTSP response) I think this was remnant from that in some way or at
>     least that's the best I can possibly imagine.
> 
>     Why the framing octet would also be listed as a 'safe' character is
>     beyond me, there were several other characters / octets which
>     definitely could have been used e.g. 0xC3 -> 0xFF.
> 
>     The fact that the document makes so many statements about ease of
>     parsing and then literally and figuratively destroy this concept
>     with bad decisions such as the framing character as well as the
>     interesting syntax for the markup.
> 
>     I will past some of those here :
> 
> 
>           1.4 <https://tools.ietf.org/html/rfc2326#section-1.4> Protocol
>           Properties
> 
> 
> 
>        RTSP has the following properties:
> 
>     ....
> 
>        Easy to parse:
>               RTSP can be parsed by standard HTTP or MIME parsers.
> 
> 
> 
>     ...
> 
> 
> 
>         4 <https://tools.ietf.org/html/rfc2326#section-4> RTSP Message
> 
> 
> 
>        RTSP is a text-based protocol and uses the ISO 10646 character set in
>        UTF-8 encoding (RFC 2279 <https://tools.ietf.org/html/rfc2279> [21]). Lines are terminated by CRLF, but
>        receivers should be prepared to also interpret CR and LF by
>        themselves as line terminators.
> 
>          Text-based protocols make it easier to add optional parameters in a
>          self-describing manner. Since the number of parameters and the
>          frequency of commands is low, processing efficiency is not a
>          concern. Text-based protocols, if done carefully, also allow easy
>          implementation of research prototypes in scripting languages such
>          as Tcl, Visual Basic and Perl.
> 
>          The 10646 character set avoids tricky character set switching, but
>          is invisible to the application as long as US-ASCII is being used.
>          This is also the encoding used for RTCP. ISO 8859-1 translates
>          directly into Unicode with a high-order octet of zero. ISO 8859-1
>          characters with the most-significant bit set are represented as
>          1100001x 10xxxxxx. (See RFC 2279 <https://tools.ietf.org/html/rfc2279> [21])
> 
>        RTSP messages can be carried over any lower-layer transport protocol
>        that is 8-bit clean.
> 
>        Requests contain methods, the object the method is operating upon and
>        parameters to further describe the method. Methods are idempotent,
>        unless otherwise noted. Methods are also designed to require little
>        or no state maintenance at the media server.
> 
> 
> 
>     This literally becomes a nightmare when you have to reconstruct TCP
>     sequences.
> 
>     I have attached a small 3MB zipped Wireshark capture which shows one
>     such case of my dealing with this issue.
> 
>     This is only exacerbated by the fact the document allows packets up
>     to the maximum holding size in this mode AND specifies that packets
>     with an unknown context must be skipped...
> 
>     Skipped how? Skipped as in past their header, past their data? Can
>     that text even be there?
> 
>     We are talking about TCP and in such a case the data from a previous
>     segment was already received by the receiver and contains only some
>     of the data how would they skip data they have yet to receive? 
> 
>     I will explain why this is a security issue, Since there is no
>     sequence information in the binary header it must be trusted to
>     contain valid length values. Without inspecting the latter octets
>     one can make no such assumption about the type of binary data
>     contained therein, especially if there is no context assigned.
> 
>     This if I can get a single TCP packet into a stream I can very
>     easily inject a lot of 'receive' space thus exponentially increasing
>     my chances of getting another packet into the stream.
> 
>     I think that there should at the very least be a correlation between
>     'Block-Size' and the frame size such that frame sizes MUST NOT ever
>     be larger than that value if not already.
> 
>     Furthermore I think that something needs to be done to specify how
>     to deal with nuisances such as 'more / less bytes available than
>     indicated in frame' especially when we also have 'Rtsp' messages
>     which can be interleaved at the same time in between frames (which
>     can contain "$").
> 
>     So to re-iterate my understanding of how things are in toto I have
>     an example I will outline below which is is a Rtsp Binary
>     Interleaved sender who tells a Rtsp Binary Interleaved client there
>     is a frame of 48344 bytes on channel 0.
> 
>     The client received only 1328 bytes.
> 
>     47016 bytes remain.
> 
>     The client starts to receive again.
> 
>     At this point there should only be the rest of the data in the frame
>     (47016 bytes)
> 
>     This data will come over several MSS sized segments, during which
>     time the socket may also be written to again (before the segment is
>     transmitted to the client).
> 
>     {
>         If the latter data happens to get to the receiver before the
>     other portions of the segment we have TCP 're-ordering' based on the
>     sequence number and may multiple ACK's for the early packets.
> 
>         If any data is missed we will have a re-transmission.
> 
>         The data being 'received' on the socket by the receiver coming
>     from the server comes from the data portion of the tcp packet which
>     now contains data from a previous segment.
>     }
> 
>     The sender is now committed to sending the additional bytes as
>     indicated however if the sender stops sending this data or it's
>     truncated it will never make to the receiver. The stack will never
>     be able to re-assemble the packet and now framing sync is lost.
> 
>     At this point ANY data consumed from the initial frame header and
>     data which was received must ALSO be dis-guarded but there is NO WAY
>     for the server to indicate this to the client... (This is why UDP is
>     commonly used, you get what you get and you don't what you don't)
> 
>     There are a lot of articles outlining why TCP and RTP don't get
>     along mostly citing the overhead of re-transmissions so with Rtsp
>     you think we would have attempted to solve this not make it worse
>     with bad encapsulation.
> 
>     Something needs to be done about this because it's also a security
>     concern, e.g. if a client were to send a rtcp packet to the server
>     which is very larger and contains no data he could attempt to
>     exhaust the resources of that server (if they didn't monitor their
>     rtcp bandwidth properly) or at least force a higher amount of traffic.
> 
>     So, information needs to be clear that there is no such thing as a
>     packet of less then 8 bytes under rtcp and 16 bytes under rtp.
>     (Unless compression is being used; ROHC or otherwise)
> 
>     The null packet or any packet under 16 bytes would used for
>     'spacing' not a 'unknown' context, especially when I can have 255
>     channels, what unknown context am I going to use then?
> 
>     That is 4 octets for the `$` header, and the rest for the the packet
>     header which can then be inspected to be the same version,
>     payloadtype and ssrc as required by the client.
> 
>     This prevents a client who may also send a "GET_PARAMETER" under
>     interleaved transport with weird headers and a body to attempt
>     underflow also which is something the current specification does
>     nothing to protect against.
> 
>     "GET_PARAMATER rtsp://someuri/ RTSP/1.0\r\nCSeq:1\r\nDate:
>     xx:xx:xx\r\nContent-Length:24\r\n$UserAgent
>     $009\r\n$\0\0\aRTSP/1.$\0\0\r\n\r\nDatawith$IsNotAGoodIdea!\0\0"
> 
>     This would allow applications to still take note of when a large
>     frame was seen but not be forced to act upon it and potentially lose
>     data, and depending on their implementation allow remote code execution.
> 
>     I urge the committee to seriously look into these issues as they can
>     have a large impact.
> 
>     https://isecpartners.github.io/fuzzing/vulnerabilities/2013/12/30/vlc-vulnerability.html
> 
>     VLC seems protected against overflow after this but with some
>     testing I have determined that not only VLC but other servers and
>     clients are vulnerable to underflow this way as well making it both
>     a server and client issue.
> 
>     I have more notes in my implementation
>     @ https://net7mma.codeplex.com/SourceControl/latest#Rtp/RtpClient.cs
>     if your interested, it relates to one issue I saw where even though
>     frame length was good other data in the packet was invalid such as
>     the 'Extension' or the 'Length In Words Minus 1' or the ssrc etc.
> 
>     Hopefully I didn't banter to much, it's rather late.
> 
>     As for my other 'issues' / errata for RFC2435 has anything been
>     determined on them?
> 
>     What about the one for RFC3550, has anyone sat down to do the math
>     on that one yet?
> 
>     Thanks again for your time and response and have a Happy New Year if
>     I don't hear back by then!
> 
>     Sincerely,
>     Julius Friedman
> 
> 
> 
>     On Tue, Dec 30, 2014 at 3:33 PM, Dale R. Worley <worley@ariadne.com
>     <mailto:worley@ariadne.com>> wrote:
> 
>         Julius Friedman <juliusfriedman@gmail.com
>         <mailto:juliusfriedman@gmail.com>> writes:
>         >  Transport           =    "Transport" ":"
>         >                             1\#transport-spec
> 
>         In a few places, RFC 2326 seems to use "\#" in place of "#".  There
>         doesn't seem to be any documentation for this.  There seems to
>         be other
>         peculiar punctuation as well, including "\$" and "$'$".
> 
>         > Since 'source' is not listed I don't know the syntax, I assumed it to
>         > be an "IPAddress" however the text sates "address" so I imagine if I
>         > found a 'source=1.2.3.4:1554 <http://1.2.3.4:1554>' that would be valid however
>         I want to
>         > make sure since there isn't any syntax specified in the RFC.
> 
>         It's not clear to me that there *is* a "source=" parameter for the
>         Transport header.  Yes, there is prose describing source as a
>         datum, but
>         there's no BNF for a corresponding parameter, and a quick search
>         doesn't
>         turn up any instance of "Transport:  ...source=..." in any RFC
>         or I-D.
> 
>         However, "source=" is shown in
>         http://heim.ifi.uio.no/~meccano/reflector/smallclient.html
> 
>         > Also I would wonder is there any restriction on specifying a port or
>         > address range also ? e.g. 'source=1.2.3.4/321202/2 <http://1.2.3.4/321202/2>'
> 
>         Well, I see "parameter = [...] ";" "destination" [ "=" address
>         ]", and
> 
>            address             =    host
> 
>            host      =   <A legal Internet host domain name of IP address
>                          (in dotted decimal form), as defined by Section 2.1
>                          of RFC 1123 \cite{rfc1123}>
> 
>         so it looks like <address> cannot specifiy an address range or a
>         port.
>         I'd expect the port to be specified by the "client_port" and
>         "server_port" parameters.
> 
>         (BTW, it looks to me like the first "of" in the definition of <host>
>         should be "or".)
> 
>         > I believe there was a similar issue with Rtp-Info headers which was
>         > fixed in 'biz' however this among other issues were not addressed and
>         > I am wondering if any other updates will be made to this RFC before
>         > 2.0 Draft is finalized.
> 
>         An RFC is never "updated", although it can be obsoleted by a
>         later RFC
>         that entirely replaces it.
> 
>         Dale
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Tue Jan 27 05:51:41 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 370BE1A8749; Tue, 27 Jan 2015 05:51:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HwX16Mo2hxMI; Tue, 27 Jan 2015 05:51:28 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 848FC1A8739; Tue, 27 Jan 2015 05:51:27 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-78-54c797dd4d50
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 8A.A7.04231.DD797C45; Tue, 27 Jan 2015 14:51:25 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.32) with Microsoft SMTP Server id 14.3.195.1; Tue, 27 Jan 2015 14:51:25 +0100
Message-ID: <54C797DC.3020609@ericsson.com>
Date: Tue, 27 Jan 2015 14:51:24 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Julius Friedman <juliusfriedman@gmail.com>, "Dale R. Worley" <worley@ariadne.com>
References: <CACFvNHXwTm5k7Wiw65A=eSBEF9RqP4FJnNysziFik7vpnqrR4A@mail.gmail.com> <87r3v38j3t.fsf@hobgoblin.ariadne.com> <CACFvNHXyCbQgx3jtzShSQGT9H-TD_Wz7bEkyOB2zfQNjof1VZw@mail.gmail.com>
In-Reply-To: <CACFvNHXyCbQgx3jtzShSQGT9H-TD_Wz7bEkyOB2zfQNjof1VZw@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCLMWRmVeSWpSXmKPExsUyM+Jvje7d6cdDDC7NtbB42bOS3eL4iSZm i6nLH7NYvDxR5sDiMXn/V2aPnbPusnssWfKTKYA5issmJTUnsyy1SN8ugStj/7MXzAWrdSpO rP/G2MD4SbGLkZNDQsBE4urC70wQtpjEhXvr2boYuTiEBI4wSpzpOQblLGeUWDvnKgtIFa+A tsTCb/+BEhwcLAKqEi96zEHCbAIWEjd/NLKB2KICwRKLnz9lhSgXlDg58wlYq4hAuMTvQ8fY QWxmoNaZ86aC2cJA8VlPtjJC7NrDKNE1ZSkzSIJTIFBix74/UA0GEkcWzWGFsOUlmrfOBqsR ArqnoamDdQKj4Cwk+2YhaZmFpGUBI/MqRtHi1OLi3HQjY73Uoszk4uL8PL281JJNjMBgPrjl t+4OxtWvHQ8xCnAwKvHwGvw/FiLEmlhWXJl7iFGag0VJnNfO+FCIkEB6YklqdmpqQWpRfFFp TmrxIUYmDk6pBkb/XoUDyjvfy1a9073WeWrmCosZPDbl27k2Bu2czXomoMRZce+ugpLb0rb9 msyd3W6NXzYs/OqUm7Yl36EshK11xgG3w/zTrGqmTrq0/N4GTgMHKTu7PHWv8KpT3/xy1jge qTOa9GNF5KLjugWLSzfYZhSUT/li92K64GK2u4flDlxa8Den66ISS3FGoqEWc1FxIgAX81Xy RwIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/zY61fiSaJgF51Pc8hsoegQWcyvo>
Cc: mmusic@ietf.org, avt@ietf.org
Subject: Re: [AVTCORE] New Possible Errata in RFC2326 (And Draft) regarding Blocksize
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jan 2015 13:51:35 -0000

Hi,

I also have some issues to see what your issue are.

The intent of this header is "can you please ensure that the media
payloads are never bigger than X". The server can either except it or
override it and respond with "No, I can only guarantee Y bytes".

And that will be dependent on both the media format and the capabilities
of the server. If the requested blocksize requires repackaging and you
don't support you will have to override the value which comes from the
packaging that do exist.

On 2015-01-10 04:38, Julius Friedman wrote:
> ...
> 
> ", it seems
> to me that it counts only the bytes after the "RTP Fixed Header Fields"
> and any RTP header extensions, and that number legitimately could be
> small (depending on the media encoding in the RTP).
> "
> 
> - There must be 12 octets which are the fixed header, this is where that
> information comes from.
> 
> - If ROHC is used or some other encoding / compression which changes
> this amount it is beyond the scope of RTP and that is why I say that the
> underlying Transport should handle this.

The text says that IP/UDP/RTP are all excluded from this so if you say
Blocksize=1 then you can only include one byte of RTP payload. Which
with the exception of some sample-based codecs are completely useless
and will have to be overridden to the minimal value the media format can
support.

But, the above appears to be irrelevant for this header.

> 
> We are not talking about other RFC's we are talking about the ones which
> state the information (RFC2326 and it's biz draft), they introduce this
> header and thus should concretely define it's functionality such that it
> does not impose upon other requirements.
> 
> I am confused as how can you both say you don't understand and that
> there is no error? It has now been explained further... Please
> re-consider, you omitted to respond to other points within the same
> email chain which relate to the problem so it imposes upon my response
> and would cause me to repeat data here again which I was asked not to
> before.
> 
> If there is a better mechanism for communication of these issues please
> let me know, I would be happy to prepare a summary and present it either
> as a document or over a tele-conference to address this as well as any
> other points which have yet to be addressed.
> 
> If there is no error then what is the process to include this useful
> information in some way so that others may know as well? 
> 
> I sincerely appreciate your time,
> Julius
> 
> 
> 
> On Fri, Jan 9, 2015 at 9:28 PM, Dale R. Worley <worley@ariadne.com
> <mailto:worley@ariadne.com>> wrote:
> 
>     Julius Friedman <juliusfriedman@gmail.com
>     <mailto:juliusfriedman@gmail.com>> writes:
>     > 18.10
>     <http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-40#section-18.10>.
>     > Blocksize
>     >
>     >    The Blocksize request-header field is sent from the client to the
>     >    media server asking the server for a particular media packet size.
>     >    This packet size does not include lower-layer headers such as IP,
>     >    UDP, or RTP.  The server is free to use a blocksize which is lower
>     >    than the one requested.  The server MAY truncate this packet size to
>     >    the closest multiple of the minimum, media-specific block size, or
>     >    override it with the media-specific size if necessary.  The block
>     >    size MUST be a positive decimal number, measured in octets.  The
>     >    server only returns an error (4xx) if the value is syntactically
>     >    invalid.
>     >
>     > Both paragraphs go to specify that the number MUST be positive but
>     > specify no LOWER bound.
>     >
>     > A Blocksize of 12 or less will cause data loss under UDP and cause
>     > invalid framing under TCP.
> 
>     Could you explain this in more detail?  Since the "Blocksize" number
>     "does not include lower-layer headers such as IP, UDP, or RTP", it seems
>     to me that it counts only the bytes after the "RTP Fixed Header Fields"
>     and any RTP header extensions, and that number legitimately could be
>     small (depending on the media encoding in the RTP).
> 
>     > It should be noted that the Blocksize MUST be a positive decimal
>     > number greater than or equal to that supported by the underlying
>     > transport.
> 
>     In any case, *this* RFC does not *have* to state that, as that is a
>     requirement imposed by other RFCs.
> 
>     > I would like to file this errata as soon as possible if everyone agrees;
>     >
>     > If it's not erratum can we please also address this misnomer I seem to have.
> 
>     As far as I can tell, it's not an erratum, because there is no "error"
>     in the RFC.  What you're suggesting is that there is useful information
>     that the RFC does not include, but that information is not an error in
>     this RFC's text.
> 
>     Dale
> 
> 
> 
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Wed Jan 28 05:20:38 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F119F1A86FF for <avt@ietfa.amsl.com>; Wed, 28 Jan 2015 05:20:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5r0Lxd-Ftr7Y for <avt@ietfa.amsl.com>; Wed, 28 Jan 2015 05:20:34 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 75D681A8702 for <avt@ietf.org>; Wed, 28 Jan 2015 05:20:32 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: avt@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150128132032.30970.80565.idtracker@ietfa.amsl.com>
Date: Wed, 28 Jan 2015 05:20:32 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/7hZiwMy6WBpgXr1JOWxRHNUkyRM>
Subject: [AVTCORE] Milestones changed for avtcore WG
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 13:20:36 -0000

Changed milestone "Submit Multipath RTP  as experimental RFC ", added
draft-ietf-avtcore-mprtp to milestone.

URL: http://datatracker.ietf.org/wg/avtcore/charter/


From nobody Wed Jan 28 07:23:13 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BAC31A00EA for <avt@ietfa.amsl.com>; Wed, 28 Jan 2015 07:23:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9L8nWwUIotTd for <avt@ietfa.amsl.com>; Wed, 28 Jan 2015 07:23:08 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 980011A0070 for <avt@ietf.org>; Wed, 28 Jan 2015 07:23:07 -0800 (PST)
X-AuditID: c1b4fb30-f79106d000001184-cf-54c8fed98f94
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 39.0D.04484.9DEF8C45; Wed, 28 Jan 2015 16:23:05 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.44) with Microsoft SMTP Server id 14.3.195.1; Wed, 28 Jan 2015 16:23:05 +0100
Message-ID: <54C8FED8.1000403@ericsson.com>
Date: Wed, 28 Jan 2015 16:23:04 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>, "avt@ietf.org" <avt@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D2E53A6@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D2E53A6@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuphluLIzCtJLcpLzFFi42KZGfG3RvfmvxMhBg8uKlu87FnJ7sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujDtT1Quus1U8vujYwLiPtYuRg0NCwERi3jvxLkZOIFNM4sK9 9WxdjFwcQgJHGCW2du1hAUkICSxnlDiwPQrE5hXQlli07SgriM0ioCoxY8tbsBo2AQuJmz8a 2UBsUYFgicXPn7JC1AtKnJz5BKxGRCBconFuM1iNsIC5xOuGvVDzfSVmv53GDmJzCvhJ9D1f DhZnFjCQOLJoDiuELS/RvHU2M0S9tkRDUwfrBEaBWUhWzELSMgtJywJG5lWMosWpxUm56UZG eqlFmcnFxfl5enmpJZsYgcF3cMtvgx2ML587HmIU4GBU4uHdEHAiRIg1say4MvcQozQHi5I4 r53xoRAhgfTEktTs1NSC1KL4otKc1OJDjEwcnFINjIFHn28ONxO4GNBec9Ar7cGvlvhU32ca b+QNePTiIxluMi+ueJnIO3HB8XvL6y4aJyU2VlYmVgSKB8/cWJLzioUjZW4+R0vN11fJHPHz 6ufPSPr6slqd4aPXCTnTtBlvVzZVtrLOEY370emo1Ht35sJ3lwv6DT4LlkWeffx4P6P+5xrz K4lflFiKMxINtZiLihMBdVdPRh8CAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/Y0p5cme4D2IdLIEciulQqEAQsFU>
Subject: Re: [AVTCORE] Errata on RFC 5764 (Errata 3913)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 15:23:10 -0000

WG,

In regards to the following Errata:

http://www.rfc-editor.org/errata_search.php?eid=3913

As we currently have a milestone and candidate WG document that proposes
to deal with this issue. I think a reasonable handling of this one would
be to put it into the "Held for Documents Update" category.

Please provide feedback by the 12th of February.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Wed Jan 28 07:29:05 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C44181A86F0 for <avt@ietfa.amsl.com>; Wed, 28 Jan 2015 07:28:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ABXLbpvHPUvE for <avt@ietfa.amsl.com>; Wed, 28 Jan 2015 07:28:40 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AB5F1A0104 for <avt@ietf.org>; Wed, 28 Jan 2015 07:28:37 -0800 (PST)
X-AuditID: c1b4fb30-f79106d000001184-88-54c900237295
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 6C.CD.04484.32009C45; Wed, 28 Jan 2015 16:28:35 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.44) with Microsoft SMTP Server id 14.3.195.1; Wed, 28 Jan 2015 16:28:35 +0100
Message-ID: <54C90022.2030307@ericsson.com>
Date: Wed, 28 Jan 2015 16:28:34 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: <mcgrew@cisco.com>, <ekr@rtfm.com>, Alissa Cooper <alissa@cooperw.in>
References: <20140422230255.290D61801A5@rfc-editor.org>
In-Reply-To: <20140422230255.290D61801A5@rfc-editor.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOLMWRmVeSWpSXmKPExsUyM+Jvja4yw8kQgzdvlCymn/nLaPGyZyW7 xYrX59gtrq76w+7A4jHl90ZWjy9PXjJ5LFnyk8lj8uM25gCWKC6blNSczLLUIn27BK6M19eO MRdMk6hYv0qigXGecBcjJ4eEgInEnn/dbBC2mMSFe+uBbC4OIYEjjBLLvixhAUkICSxnlJh9 ygzE5hXQlmhsaGMCsVkEVCW65l0Aa2YTsJC4+aMRzBYVCJZY/PwpK0S9oMTJmU/A5ogIeEpM Xd/OCGIzCwhJnJ7zDaiGg0NYwFHi3Q5FiFXmEh0PusDGcAKNnHbgAztEuYHEkUVzWCFseYnm rbOZIeq1JRqaOlgnMArOQrJtFpKWWUhaFjAyr2IULU4tTspNNzLSSy3KTC4uzs/Ty0st2cQI DOmDW34b7GB8+dzxEKMAB6MSD++GgBMhQqyJZcWVuYcYpTlYlMR57YwPhQgJpCeWpGanphak FsUXleakFh9iZOLglGpgTGhZ8315Ven2hPvaSZxOEzdPVtrcnbRh2+zAGbEpV/a6Hlp0Uo1F 5upquwiO9fO2GZkeSLzo7TPh/iXpU5s/rJWUmPh9IvPjDaHFs3VDhZccPDqZZ3mv6+EntUEe /ZLsl2dFz12QHLn7fnbGhSMndr648/LMCm3rfc0SAk01bc0rxBdt937q90OJpTgj0VCLuag4 EQDFYJWdSgIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/nUZ0rwC1FHPTLLitRt7iVbXTVhA>
Cc: avt@ietf.org
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC5764 (3971)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 15:28:55 -0000

WG, EKR and David

Without having any deep knowledge of TLS, this errata appears to be
correct and minor potential source of confusion. Thus, I would propose
that we put this on into "Verified" status. I would appreciate if EKR
could confirm this as being valid.

WG, please provide feedback by the 12th of February.

Cheers

Magnus Westerlund


On 2014-04-23 01:02, RFC Errata System wrote:
> The following errata report has been submitted for RFC5764,
> "Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5764&eid=3971
> 
> --------------------------------------
> Type: Technical
> Reported by: Martin Thomson <martin.thomson@gmail.com>
> 
> Section: 4.1.3
> 
> Original Text
> -------------
>    If the client detects a nonzero-length MKI in the server's response
>    that is different than the one the client offered, then the client
>    MUST abort the handshake and SHOULD send an invalid_parameter alert.
> 
> Corrected Text
> --------------
>    If the client detects a nonzero-length MKI in the server's response
>    that is different than the one the client offered, then the client
>    MUST abort the handshake and SHOULD send an illegal_parameter alert.
> 
> Notes
> -----
> invalid_parameter isn't defined anywhere; this probably means illegal_parameter(47), which is defined in RFC 5246.
> 
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC5764 (draft-ietf-avt-dtls-srtp-07)
> --------------------------------------
> Title               : Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)
> Publication Date    : May 2010
> Author(s)           : D. McGrew, E. Rescorla
> Category            : PROPOSED STANDARD
> Source              : Audio/Video Transport
> Area                : Real-time Applications and Infrastructure
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Wed Jan 28 07:39:43 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03FA31A8733 for <avt@ietfa.amsl.com>; Wed, 28 Jan 2015 07:39:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MKRC03-OA_0D for <avt@ietfa.amsl.com>; Wed, 28 Jan 2015 07:39:40 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0E0D1A1EF6 for <avt@ietf.org>; Wed, 28 Jan 2015 07:39:39 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-f4-54c902b94cba
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id E4.C6.04231.9B209C45; Wed, 28 Jan 2015 16:39:37 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.68) with Microsoft SMTP Server id 14.3.195.1; Wed, 28 Jan 2015 16:39:37 +0100
Message-ID: <54C902B9.2000308@ericsson.com>
Date: Wed, 28 Jan 2015 16:39:37 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: <caceres@watson.ibm.com>, <alan@telchemy.com>, <timur.friedman@lip6.fr>
References: <20131111125230.63AF875E015@rfc-editor.org>
In-Reply-To: <20131111125230.63AF875E015@rfc-editor.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUyM+Jvje5OppMhBl+/mVpcu9fPbjH9zF9G i5c9K9ktLt+5zmhxZ8YOdgdWjy9PXjJ5LFnyk8lj75Ysj2PzzzF6nNtoHMAaxWWTkpqTWZZa pG+XwJXxb9V5loJlIhXvX2U2MDYLdDFyckgImEgc2XuZFcIWk7hwbz1bFyMXh5DAEUaJRdNX sEM4yxkl1n07DFbFK6At8fDmb3YQm0VAVeJY4ycWEJtNwELi5o9GNhBbVCBYYvHzp1D1ghIn Zz4BquHgEBHwlli0TgskzCxgKvGnbyNYq7CAucT1GxeYQWwhIPvrvKVgrZxAI+d8WsIGUW8g cWTRHFYIW16ieetsqHptiYamDtYJjIKzkGybhaRlFpKWBYzMqxhFi1OLi3PTjYz1Uosyk4uL 8/P08lJLNjECg/zglt+6OxhXv3Y8xCjAwajEw7sh4ESIEGtiWXFl7iFGaQ4WJXFeO+NDIUIC 6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoYV5RNW//mmtibxMcfKsqVD2q4z9sRuG+NVOeHnHu7 Vr5/qmzZqed/VqzFaBd35yuea6aVd5ZcfbI5+ouI0Rvx4915iW9UUo2O3nPZvDNl7qqyH2e4 /0QcWjRd+4CncrYnX6f4rLkd+/6/Km9Kq8j9NOV7XWNv4g3OhgW5C47mK++cJBT45antZCWW 4oxEQy3mouJEANuD/xBTAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/rgKMXMDzeTjESuMOnIy-QPaJiT0>
Cc: avt@ietf.org
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC3611 (3795)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 15:39:42 -0000

WG,

Based on the discussion in the MMUSIC WG I draw the conclusion that this
Errata shall be Verified.

Any comments on this, please provide them by the 12th of February.

Cheers

Magnus


On 2013-11-11 13:52, RFC Errata System wrote:
> The following errata report has been submitted for RFC3611,
> "RTP Control Protocol Extended Reports (RTCP XR)".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3611&eid=3795
> 
> --------------------------------------
> Type: Technical
> Reported by: Stephen James <sjames@genband.com>
> 
> Section: 5.1
> 
> Original Text
> -------------
> rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF
> 
> Corrected Text
> --------------
> rtcp-xr-attrib = "a=" "rtcp-xr" [ ":" xr-format *(SP xr-format)] CRLF
> 
> Notes
> -----
> The ABNF for the attribute is causing some interoperability issues.
> The text as written shows that the colon is required while the parameters are optional.
> This leaves the format: "a=rtcp-xr:" the required format.  Vendors are using "a=rtcp-xr" which strictly violates the ABNF above. Moving the ':' into the optional part seems correct.
> 
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC3611 (draft-ietf-avt-rtcp-report-extns-06)
> --------------------------------------
> Title               : RTP Control Protocol Extended Reports (RTCP XR)
> Publication Date    : November 2003
> Author(s)           : T. Friedman, Ed., R. Caceres, Ed., A. Clark, Ed.
> Category            : PROPOSED STANDARD
> Source              : Audio/Video Transport
> Area                : Real-time Applications and Infrastructure
> Stream              : IETF
> Verifying Party     : IESG
> 
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Wed Jan 28 07:43:33 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68BF51A8709 for <avt@ietfa.amsl.com>; Wed, 28 Jan 2015 07:43:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N2qPrC0PNVma for <avt@ietfa.amsl.com>; Wed, 28 Jan 2015 07:43:29 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B08F41A86EB for <avt@ietf.org>; Wed, 28 Jan 2015 07:43:28 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-cc-54c9039e105c
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 07.29.04076.E9309C45; Wed, 28 Jan 2015 16:43:27 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.38) with Microsoft SMTP Server id 14.3.195.1; Wed, 28 Jan 2015 16:43:26 +0100
Message-ID: <54C9039E.1080105@ericsson.com>
Date: Wed, 28 Jan 2015 16:43:26 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: <schulzrinne@cs.columbia.edu>, <casner@acm.org>, <ronf@bluecoat.com>, <van@packetdesign.com>, <rlb@ipv.sx>, <alissa@cooperw.in>
References: <20141204014737.6282D181CD3@rfc-editor.org>
In-Reply-To: <20141204014737.6282D181CD3@rfc-editor.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrHLMWRmVeSWpSXmKPExsUyM+Jvje585pMhBqu6WC2mn/nLaPGyZyW7 xYtVc1gsjp9oYraY2mdrcX7DZTaLS/9ULL6dvc3qwOFx+Yq3x8sXN1k9vjx5yeTx9dZBJo+d s+6yeyxZ8pPJY/LGWSweE5p3sgVwRHHZpKTmZJalFunbJXBlLHz7lLXgo0zF0wsv2BoYD4t1 MXJySAiYSMy7MYcZwhaTuHBvPRuILSRwhFHi9pGgLkYuIHs5o8SildPAErwC2hJ/ZuxmAbFZ BFQlDj/8CxZnE7CQuPmjEcwWFQiWWPz8KStEvaDEyZlPWEAGiQi0MkqsbX4FlmAW0JPYeb+J HcQWFnCUWLz0JWMXIwfQNnOJZxvlQcKcQDOv3tnDBlFuIHFk0RyoVnmJ5q2zmSEO1ZZoaOpg ncAoOAvJullIWmYhaVnAyLyKUbQ4tbg4N93ISC+1KDO5uDg/Ty8vtWQTIzBCDm75bbWD8eBz x0OMAhyMSjy8GwJOhAixJpYVV+YeYpTmYFES57UzPhQiJJCeWJKanZpakFoUX1Sak1p8iJGJ g1OqgXEju0h59f1/Ab3HeKSeif+xlpyuP13Hjt+tMIpj0v0mzclRL5L6ORU3z5qQsmWdaKsE q84Bnz3LpRTlVzm+05PflPPn5+WY3F6mi++fl0b80NlVWlu41uaU/stec/HuBNcnlspvgif3 Ctc9Kz28Tyxq84eH32aeO2xrLjLLcZLt4c7poUJiz5RYijMSDbWYi4oTAXhv4XVxAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/8JAgQi6xplZilVFfZueBUcRxV8Q>
Cc: juliusfriedman@gmail.com, avt@ietf.org
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC3550 (4192)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 15:43:31 -0000

WG,

There has been quite some discussion. There appear to be substantial
support for putting this Errata into the "Rejected" state.

Any additional feedback, please provided it by the 12th of February.

Cheers

Magnus

On 2014-12-04 02:47, RFC Errata System wrote:
> The following errata report has been submitted for RFC3550,
> "RTP: A Transport Protocol for Real-Time Applications".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3550&eid=4192
> 
> --------------------------------------
> Type: Technical
> Reported by: Julius Friedman <juliusfriedman@gmail.com>
> 
> Section: 6.4.1
> 
> Original Text
> -------------
> sender's octet count: 32 bits
>       The total number of payload octets (i.e., not including header or
>       padding) transmitted in RTP data packets by the sender since
>       starting transmission up until the time this SR packet was
>       generated.  The count SHOULD be reset if the sender changes its
>       SSRC identifier.  This field can be used to estimate the average
>       payload data rate.
> 
> Corrected Text
> --------------
> sender's octet count: 32 bits
>       The total number of payload octets 
>       transmitted in RTP data packets by the sender since
>       starting transmission up until the time this SR packet was
>       generated.  The count SHOULD be reset if the sender changes its
>       SSRC identifier.  This field can be used to estimate the average
>       payload data rate.
> 
> Notes
> -----
> Where as payload octets is defined as the total number of data octets contained in a Rtp Packet minus the 12 Header octets for Rtp Packets.
> 
> Padding octets as well as octets which occur in the contributing source list should also be included as they may differ on a per packet basis and would make the total calculation invalid.
> 
> During TCP communication any application layer header should NOT be included in the total bytes count when including the header length.
> 
> Any Rtcp packet counters should include the total length of the packet (header, padding and any other data).
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC3550 (draft-ietf-avt-rtp-new-12)
> --------------------------------------
> Title               : RTP: A Transport Protocol for Real-Time Applications
> Publication Date    : July 2003
> Author(s)           : H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson
> Category            : DRAFT STANDARD
> Source              : Audio/Video Transport
> Area                : Real-time Applications and Infrastructure
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Wed Jan 28 08:09:24 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 370441A1EF6 for <avt@ietfa.amsl.com>; Wed, 28 Jan 2015 07:47:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id woPWDkaRlDXE for <avt@ietfa.amsl.com>; Wed, 28 Jan 2015 07:47:30 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B70CD1A1B01 for <avt@ietf.org>; Wed, 28 Jan 2015 07:47:29 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-33-54c9048fa13a
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 0B.A9.04076.F8409C45; Wed, 28 Jan 2015 16:47:28 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.47) with Microsoft SMTP Server id 14.3.195.1; Wed, 28 Jan 2015 16:47:27 +0100
Message-ID: <54C9048F.1000509@ericsson.com>
Date: Wed, 28 Jan 2015 16:47:27 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: <berc@pa.dec.com>, <fenner@parc.xerox.com>, <frederick@parc.xerox.com>, <mccanne@cs.berkeley.edu>, <stewart@parc.xerox.com>, <rlb@ipv.sx>, <alissa@cooperw.in>, <keith.drage@alcatel-lucent.com>, <roni.even@mail01.huawei.com>
References: <20140904164839.0F554180450@rfc-editor.org>
In-Reply-To: <20140904164839.0F554180450@rfc-editor.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGLMWRmVeSWpSXmKPExsUyM+Jvje4ElpMhBt96OCymn/nLaPGyZyW7 xbze42wWs9evZLXY0vuNzeL4iSZmi6eNZxkt7rcdZraY2mdr8aTlB7NFy4t9LA7cHq3P9rJ6 fHnyksljwsnz7B47Z91l91iy5CeTx+SNs1g8dmx+wOoxb/JVZo/eSf8ZAzijuGxSUnMyy1KL 9O0SuDI6ux6wFeyWqbjQMYupgbFVrIuRk0NCwETi98c2VghbTOLCvfVsXYxcHEICRxglZvfO Y4FwljNKTJ/3gwWkildAW2Lf7N1gHSwCqhJ7L/9lB7HZBCwkbv5oZAOxRQWCJRY/f8oKUS8o cXLmE7BBIgIvGSWu3zkI1sAsoCex834TmC0s4Cix6P5aZhBbSMBc4vOzD4wgNifQ0GefzrJA 1BtIHFk0hxXClpdo3jobql5boqGpg3UCo+AsJPtmIWmZhaRlASPzKkbR4tTi4tx0IyO91KLM 5OLi/Dy9vNSSTYzAiDq45bfVDsaDzx0PMQpwMCrx8G4IOBEixJpYVlyZe4hRmoNFSZzXzvhQ iJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbGyuQiHrvo5/bXrRun72D9skTjg5HzTZeySqGv V+/L6EvejEvk2XM+Sep4h7Da5KcufLr74ud8qmnO1glL0+BJurv6P8+OV4JsTW1mjNbJwXtM WsOPtZ/3OFOb8kPCb/pMoVfbkzc4ijpGbpzOz++XI7Nzd4Q1r/j29wo/rPfkPCq8vTCWLUiJ pTgj0VCLuag4EQDfyJwxiQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/22SKWmSdiWysskL4armw72GVE_Y>
X-Mailman-Approved-At: Wed, 28 Jan 2015 08:09:08 -0800
Cc: juliusfriedman@gmail.com, avt@ietf.org
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC2435 (4097)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 15:47:32 -0000

WG,

My proposal is that this Errata is "Rejected" based on that its section
of change does not contain any change. And the notes part proposed
changed is a redefinition of a field, i.e. something that would require
a replacement RFC to change.

Please provide any comments by the 12th of February.

Cheers

Magnus Westerlund
WG chair


On 2014-09-04 18:48, RFC Errata System wrote:
> The following errata report has been submitted for RFC2435,
> "RTP Payload Format for JPEG-compressed Video".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=2435&eid=4097
> 
> --------------------------------------
> Type: Technical
> Reported by: Julius Richard Friedman <juliusfriedman@gmail.com>
> 
> Section: 3.1.5
> 
> Original Text
> -------------
> 3.1.5.  Width: 8 bits
> 
>    This field encodes the width of the image in 8-pixel multiples (e.g.,
>    a width of 40 denotes an image 320 pixels wide).  The maximum width
>    is 2040 pixels.
> 
> 3.1.6.  Height: 8 bits
> 
>    This field encodes the height of the image in 8-pixel multiples
>    (e.g., a height of 30 denotes an image 240 pixels tall). When
>    encoding interlaced video, this is the height of a video field, since
>    fields are individually JPEG encoded. The maximum height is 65535
>    pixels.
> 
> Corrected Text
> --------------
> 3.1.5.  Width: 8 bits
> 
>    This field encodes the width of the image in 8-pixel multiples (e.g.,
>    a width of 40 denotes an image 320 pixels wide).  The maximum width
>    is 2040 pixels.
> 
> 3.1.6.  Height: 8 bits
> 
>    This field encodes the height of the image in 8-pixel multiples
>    (e.g., a height of 30 denotes an image 240 pixels tall). When
>    encoding interlaced video, this is the height of a video field, since
>    fields are individually JPEG encoded. The maximum height is 65535
>    pixels.
> 
> Notes
> -----
> Use a divisor of 256 to determine the height, where 8 / 256 = 32.
> 
> Ensure FragmentOffset does not exceed 2^24, if it does then use 2^24 - value)
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC2435 (no draft string recorded)
> --------------------------------------
> Title               : RTP Payload Format for JPEG-compressed Video
> Publication Date    : October 1998
> Author(s)           : L. Berc, W. Fenner, R. Frederick, S. McCanne, P. Stewart
> Category            : PROPOSED STANDARD
> Source              : Audio/Video Transport
> Area                : Real-time Applications and Infrastructure
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Jan 29 03:03:01 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E92A21A01F6; Thu, 29 Jan 2015 03:02:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Cd2VrkUHdkQ; Thu, 29 Jan 2015 03:02:56 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 147121A00CD; Thu, 29 Jan 2015 03:02:55 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-39-54ca135e4345
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 6C.04.24955.E531AC45; Thu, 29 Jan 2015 12:02:54 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.65) with Microsoft SMTP Server id 14.3.195.1; Thu, 29 Jan 2015 12:02:53 +0100
Message-ID: <54CA135D.3020304@ericsson.com>
Date: Thu, 29 Jan 2015 12:02:53 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: David McGrew <mcgrew@cisco.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <20141029122825.18943.78129.idtracker@ietfa.amsl.com> <3C4AAD4B5304AB44A6BA85173B4675CABC709A18@MSMR-GH1-UEA03.corp.nsa.gov> <545151F9.9050502@cs.tcd.ie> <B1821703-9D09-41C5-AAC1-5EBB9CE2ACC4@cisco.com> <54516572.8020601@cs.tcd.ie> <D825D4F3-26D3-49BE-9E32-0E4FFF89BC40@cisco.com> <5451737B.6060504@cs.tcd.ie> <2D4BE3ED-840A-444C-9D18-09BC3D937D64@cisco.com>
In-Reply-To: <2D4BE3ED-840A-444C-9D18-09BC3D937D64@cisco.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLLMWRmVeSWpSXmKPExsUyM+JvjW6c8KkQg78HJS1e9qxkt1j57Tqr xdojiRYz/kxktphw6jWrxdVVf9gtpu+9xu7A7jHl90ZWj7XdV9k8liz5yeTRv+slq8eXy5/Z AlijuGxSUnMyy1KL9O0SuDLa9k1mLPgiXjG7cwdLA+M24S5GTg4JAROJtlWTmSBsMYkL99az dTFycQgJHGGUODF9CTuEs5xRYvmO5WwgVbwC2hLvTs9iBLFZBFQlNmxsAetmE7CQuPmjEaxG VCBYYvHzp6wQ9YISJ2c+YQGxRQSCJFbu+AUWZxboZJLY058OYgsLxEnMermJHcQWEvjEJHHp vxWIzSlgK/HvzEw2iHoDiSOL5kD1yks0b53NDFGvLdHQ1ME6gVFwFpJ1s5C0zELSsoCReRWj aHFqcVJuupGxXmpRZnJxcX6eXl5qySZGYPgf3PJbdQfj5TeOhxgFOBiVeHgNFp0MEWJNLCuu zD3EKM3BoiTOa2d8KERIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QDY4aE21KX11Wma7QXyU7u 7f/iUxzX/u/as+a4z79yjvrMmSt8PWTzrpg/N/ftuL+pw7epwkjghEdhZPPUKVW3buzQm9DR WbjgnbTFuiUW4e33XRgC3vJcz1605FTYdu22kt/H0zl9cmcxJ4RJLTy2xmI9g8GGEo27voof azq46gNtLlfc2ds7V4mlOCPRUIu5qDgRAEpsII1gAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/596iZw9f1vs6INhTI89Om0W2HUg>
Cc: "avtcore-chairs@tools.ietf.org" <avtcore-chairs@tools.ietf.org>, "draft-ietf-avtcore-srtp-aes-gcm@tools.ietf.org" <draft-ietf-avtcore-srtp-aes-gcm@tools.ietf.org>, The IESG <iesg@ietf.org>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] Stephen Farrell's Discuss on draft-ietf-avtcore-srtp-aes-gcm-14: (with DISCUSS)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 11:02:59 -0000

Hi Stephen, All,

(Adding the AVTCORE WG): WG there are feedback requested from you below!

I am taking over as shepherd for this document and would like to make
some progress here.

I would like to make some observations around the discuss.
https://datatracker.ietf.org/doc/draft-ietf-avtcore-srtp-aes-gcm/ballot/#stephen-farrell

First, that Stephen appear to grouping AES-GCM and AES-CCM into one
bucket. From my perspective they are defined as two different ciphers
for SRTP but within a single document. One can implement either of them
without any requirement on implementing the other from this document.

Each of them have MTI requirements on configurations that MUST be
supported if one support that particular cipher. That is defined as
strongest for each key length.

>From the draft:

Section 13.1:

   Any implementation of AES-GCM SRTP MUST support both AEAD_AES_128_GCM
   and AEAD_AES_256_GCM (the versions with 16 octet AEAD authentication
   tags), and it MAY support the four other variants shown in table 1.

Section 13.2:

   Any implementation of AES-CCM SRTP/SRTCP MUST support both
   AEAD_AES_128_CCM and AEAD_AES_256_CCM (the versions with 16 octet
   AEAD authentication tags), and MAY support the other four variants.

I would further also note that to make anything MTI for SRTP independent
on deployment and usage, then a document must Update the MTI definition
in RFC 3711, something that hasn't been done yet. So far it is up to the
umbrella specifications, like WebRTC etc as discussed in SRTP not
mandatory document (RFC 7202) to define what ciphers that MUST be
implemented. And if we are updating RFC 3711 the mandatory to implement
for any SRTP implementation will certainly be a question.


When it comes to the core of your discuss if these 4 (AES-GCM) + 6
(AES-CCM) options must be defined. That is difficult question. One which
is difficult to answer within the context of the WG actually. As David
has raised in the private discussion so far there will be people that
will argue anything other than the longest tags and keys are acceptable,
others will note that using the 16 byte authentication tags do results
in the authentication data being more than the RTP payload (single audio
frame) for a number of the audio formats we have. Me personally I think
I would remove the 12 bytes tag-length from AES-CCM to reduce the number
of options. But two tag-lengths and two key-lengths do not appear
excessive.

WG, the chairs and ADs appreciate feedback on your view here.


Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Jan 29 04:28:28 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC76F1A01D8 for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 04:28:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GAaaAz-6WgN5 for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 04:28:23 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB7901A0033 for <avt@ietf.org>; Thu, 29 Jan 2015 04:28:22 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-39-54ca2764f339
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id B0.13.04231.4672AC45; Thu, 29 Jan 2015 13:28:20 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.53) with Microsoft SMTP Server id 14.3.195.1; Thu, 29 Jan 2015 13:28:20 +0100
Message-ID: <54CA2764.9040103@ericsson.com>
Date: Thu, 29 Jan 2015 13:28:20 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B1D2E53A6@ESESSMB209.ericsson.se>	<CABkgnnWK0jtXy1hAd7n2gEj6+ifdksZyT7QgNwqB0nje1Y4SpQ@mail.gmail.com>	<536356B3.8010000@ericsson.com> <CABkgnnUaiXi4jzNGdOodaPVZUPH09Vy3TzxObiRzq46XGtRwYA@mail.gmail.com> <53673293.7030700@ericsson.com>
In-Reply-To: <53673293.7030700@ericsson.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUyM+JvjW6K+qkQg5snLCxe9qxkt7h25h+j A5PHzll32T2WLPnJFMAUxWWTkpqTWZZapG+XwJWx99US1oJJ0hWPf/ezNzA+E+1i5OSQEDCR WLj/JTuELSZx4d56ti5GLg4hgSOMEldfd0E5yxklrn3dyAZSxSugLbFwzyNWEJtFQFXi66oJ jCA2m4CFxM0fjWA1ogLBEoufP2WFqBeUODnzCQuILSKgK7Ho7AOgbRwczAKKEpPaJUHCwgLW EtPXf2WH2DWdSWL93rdgvZwCOhIv7j5ghqjXlFi/Sx8kzCwgL9G8dTYziC0EdE5DUwfrBEbB WUi2zULomIWkYwEj8ypG0eLU4uLcdCNjvdSizOTi4vw8vbzUkk2MwGA9uOW37g7G1a8dDzEK cDAq8fAaLDoZIsSaWFZcmXuIUZqDRUmc1874UIiQQHpiSWp2ampBalF8UWlOavEhRiYOTqkG Rk19sw+7PXdeWRwjxN/m/XaxTfSl46xHDhUd25GTZPybj8+L77wE/6n/v1M7PfLYj64sOc9/ acNa0b2Tb575eSzrzhFXeSeN5w46X04+8L4g8eKxeSnDD+lXT9hN2w88UT4/WT7InvFNdNz1 s9kX0v2rLtfIpLo9u3nn/hQTT6HPwceMd/87vUSJpTgj0VCLuag4EQCzfW0XNwIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/uLos6DfiuHyLtyRw0q-18FZ3Zxw>
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Errata on RFC 5764 : Errata ID: 3913
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 12:28:26 -0000

WG,

Based on this discussion it appears that the conclusion was to Reject
this errata. We have ongoing document work that will address this issue,
so approving it would be to get ahead of that work. Secondly, held for
document update appears possible, but also unnecessary now that the work
actually is happening.

So this will be requested to be rejected by the AD, unless someone
speaks up before the 13th of February.

Cheers

Magnus
WG chair

On 2014-05-05 08:41, Magnus Westerlund wrote:
> On 2014-05-02 19:10, Martin Thomson wrote:
>> On 2 May 2014 01:26, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:
>>> 1. To any in the WG: Do you really think there is an issue of
>>> restricting STUN to 128 methods per class per existing RFC?
>>
>> This is an alternative to what I proposed, which would leave 5764
>> alone.  You need to make some allowance for this though:
>> http://www.iana.org/assignments/stun-parameters/stun-parameters.xhtml#stun-parameters-2
>>  (Note the range 0x800-0xFFF, which is currently unused)
> 
> 
> Yes, and from my personal position, I think it is fine to leave RFC 5764
> alone here. The 128 methods per class should be sufficient.
> 
> But I do agree that we should work to ensure that these limitations are
> reflected in STUN's IANA section.
> 
>>
>>> 2. To Martin: What made you think there was an error in RFC 5764?
>>
>> This:
>>
>>> Formally this is a value overlap between what STUN could potentially use
>>> (0-63) and what DTLS can potentially use 20-63.
>>
>> I don't think that it's quite fair to say that it's a fault of STUN.
>> STUN was there first, so arguably the fault lies with RFC 5764.
> 
> Agreed, but it was a decision that was discussed in the community when
> it happened.
> 
>>
>> As I said, it's a minor issue.  There doesn't seem to be any need for
>> the overlap, so it's probably safe to retroactively change the rules
>> for STUN method registrations.
>>
> 
> I also think so. And, I think the minimal work needed here is to address
> STUN's IANA rules within the TRAM WG, not also change values in RFC
> 5764. Therefore I would like to reject this Errata.
> 
> I will give everyone two weeks to think this over and object against my
> proposal to reject the errata.
> 
> Cheers
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Jan 29 04:30:03 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 641361A01D8 for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 04:30:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4tDdMYw-STiv for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 04:29:58 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBE781A0033 for <avt@ietf.org>; Thu, 29 Jan 2015 04:29:57 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-ec-54ca27c49451
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id CB.53.04231.4C72AC45; Thu, 29 Jan 2015 13:29:56 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.89) with Microsoft SMTP Server id 14.3.195.1; Thu, 29 Jan 2015 13:29:55 +0100
Message-ID: <54CA27C3.2070708@ericsson.com>
Date: Thu, 29 Jan 2015 13:29:55 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B1D2E53A6@ESESSMB209.ericsson.se>	<CABkgnnWK0jtXy1hAd7n2gEj6+ifdksZyT7QgNwqB0nje1Y4SpQ@mail.gmail.com>	<536356B3.8010000@ericsson.com> <CABkgnnUaiXi4jzNGdOodaPVZUPH09Vy3TzxObiRzq46XGtRwYA@mail.gmail.com> <53673293.7030700@ericsson.com> <54CA2764.9040103@ericsson.com>
In-Reply-To: <54CA2764.9040103@ericsson.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUyM+Jvje4R9VMhBie+8Fu87FnJbnHtzD9G ByaPnbPusnssWfKTKYApissmJTUnsyy1SN8ugStj/6e/zAUrZCs+Hl/H3MB4WryLkZNDQsBE 4u2GCewQtpjEhXvr2boYuTiEBI4wSuyc1cUM4SxnlFi4exYrSBWvgLZEz7l2MJtFQFVi1dH3 jCA2m4CFxM0fjWwgtqhAsMTi50+h6gUlTs58wgJiiwjoSiw6+wBoGwcHs4CixKR2SZCwsIC1 xPT1X9khdm1nkth2+hXYHE4BHYll304yQ9RrSqzfpQ8SZhaQl2jeOpsZxBYCOqehqYN1AqPg LCTbZiF0zELSsYCReRWjaHFqcXFuupGxXmpRZnJxcX6eXl5qySZGYLAe3PJbdwfj6teOhxgF OBiVeHgNFp0MEWJNLCuuzD3EKM3BoiTOa2d8KERIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QD Y27k9+pHAQtL2B8ddXgjY/J2282PVp987kz+U3PC7X/ilzyBl4rF1crRihE+h0s4rhuocDe1 chzj8eOL45/MyzWtO16umnczS8Y7Vs35x145bbzu/2K/85039dEfpU5kPToc+u/NjT/dIkXz 6juup/n+DqjefGWROau80wT2H4o7nGVN5i9do8RSnJFoqMVcVJwIAHMQssg3AgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/18ci9J8L0SD29SKOBwpOZp_lW98>
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Errata on RFC 5764 : Errata ID: 3913
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 12:30:00 -0000

Sorry, for confusing you.

I already sent another email on this. Lets go with the previous emails
Held for Document Update.

/Magnus

On 2015-01-29 13:28, Magnus Westerlund wrote:
> WG,
> 
> Based on this discussion it appears that the conclusion was to Reject
> this errata. We have ongoing document work that will address this issue,
> so approving it would be to get ahead of that work. Secondly, held for
> document update appears possible, but also unnecessary now that the work
> actually is happening.
> 
> So this will be requested to be rejected by the AD, unless someone
> speaks up before the 13th of February.
> 
> Cheers
> 
> Magnus
> WG chair
> 
> On 2014-05-05 08:41, Magnus Westerlund wrote:
>> On 2014-05-02 19:10, Martin Thomson wrote:
>>> On 2 May 2014 01:26, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:
>>>> 1. To any in the WG: Do you really think there is an issue of
>>>> restricting STUN to 128 methods per class per existing RFC?
>>>
>>> This is an alternative to what I proposed, which would leave 5764
>>> alone.  You need to make some allowance for this though:
>>> http://www.iana.org/assignments/stun-parameters/stun-parameters.xhtml#stun-parameters-2
>>>  (Note the range 0x800-0xFFF, which is currently unused)
>>
>>
>> Yes, and from my personal position, I think it is fine to leave RFC 5764
>> alone here. The 128 methods per class should be sufficient.
>>
>> But I do agree that we should work to ensure that these limitations are
>> reflected in STUN's IANA section.
>>
>>>
>>>> 2. To Martin: What made you think there was an error in RFC 5764?
>>>
>>> This:
>>>
>>>> Formally this is a value overlap between what STUN could potentially use
>>>> (0-63) and what DTLS can potentially use 20-63.
>>>
>>> I don't think that it's quite fair to say that it's a fault of STUN.
>>> STUN was there first, so arguably the fault lies with RFC 5764.
>>
>> Agreed, but it was a decision that was discussed in the community when
>> it happened.
>>
>>>
>>> As I said, it's a minor issue.  There doesn't seem to be any need for
>>> the overlap, so it's probably safe to retroactively change the rules
>>> for STUN method registrations.
>>>
>>
>> I also think so. And, I think the minimal work needed here is to address
>> STUN's IANA rules within the TRAM WG, not also change values in RFC
>> 5764. Therefore I would like to reject this Errata.
>>
>> I will give everyone two weeks to think this over and object against my
>> proposal to reject the errata.
>>
>> Cheers
>>
>> Magnus Westerlund
>>
>> ----------------------------------------------------------------------
>> Services, Media and Network features, Ericsson Research EAB/TXM
>> ----------------------------------------------------------------------
>> Ericsson AB                 | Phone  +46 10 7148287
>> FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>> ----------------------------------------------------------------------
>>
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>>
> 
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Jan 29 04:46:30 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67C401A0378 for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 04:46:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z1msneKgy3VB for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 04:46:23 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F15251A0364 for <avt@ietf.org>; Thu, 29 Jan 2015 04:46:22 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-9f-54ca2b9ca8c5
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 35.58.24955.C9B2AC45; Thu, 29 Jan 2015 13:46:20 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.44) with Microsoft SMTP Server id 14.3.195.1; Thu, 29 Jan 2015 13:46:20 +0100
Message-ID: <54CA2B9C.2090208@ericsson.com>
Date: Thu, 29 Jan 2015 13:46:20 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: <alissa@cooperw.in>
References: <20140904143352.2EB3218047E@rfc-editor.org>
In-Reply-To: <20140904143352.2EB3218047E@rfc-editor.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrPLMWRmVeSWpSXmKPExsUyM+Jvje4c7VMhBkf+W1pMP/OX0eJlz0p2 i+MnmpgdmD2+PHnJ5LFz1l12jyVLfjIFMEdx2aSk5mSWpRbp2yVwZdxerVTQpVHx93ErWwPj RNkuRk4OCQETiZl/TrBB2GISF+6tB7K5OIQEjjBKzH2yGspZziixf99UVpAqXgFtiaerlrCA 2CwCqhIrVr1gArHZBCwkbv5oBJskKhAssfj5U6h6QYmTM5+A1YsIiEusbNwCZjML6EnsvN/E DmILCzhKLDkzgxnEFhIwl9h5dgmYzQk089Xs1ewQ9QYSRxbNYYWw5SWat86GqteWaGjqYJ3A KDgLybpZSFpmIWlZwMi8ilG0OLU4KTfdyFgvtSgzubg4P08vL7VkEyMwhA9u+a26g/HyG8dD jAIcjEo8vAaLToYIsSaWFVfmHmKU5mBREue1Mz4UIiSQnliSmp2aWpBaFF9UmpNafIiRiYNT qoExcNbcffNn1E20XZ5fa3xTmo3ZNCb7TflyucLbGV5avCpVHHX+P/5MZbnsvnSOYReLi/2z 3gftdQH8GiveaNrqiCnujXC8/cz1YMme+/mV1ZO1ol8WVhzufH+DpaNHa/l9i6zl2nuV/856 8ViKXVV2xWWGG7ctV9t/W+yv+rXc9qRPkV3uv3lKLMUZiYZazEXFiQCOskeUQgIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/W2t8gAeIx5CNGe1XpU3b1W0lgHY>
Cc: juliusfriedman@gmail.com, avt@ietf.org
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC2435 (4094)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 12:46:26 -0000

WG,

I need your input on this Errata. Should it be held for document update
or Rejected?

The reason I think we can exclude the Verified option is that these
table are verbatim from Annex K.1 of the JPEG specficiation (ISO/IEC
10918-1 : 1993(E)). I would also note the initial text in that annex
preceding the tables:

   Two examples of quantization tables are given in Tables K.1 and K.2.
These are based on psychovisual thresholding and are derived empirically
using luminance and chrominance and 2:1 horizontal subsampling. These
tables are provided as examples only and are not necessarily suitable
for any particular application. These quantization values have been
used with good results on 8-bit per sample luminance and chrominance
images of the format illustrated in Figure 13. Note that these
quantization values are appropriate for the DCT normalization defined in
A.3.3.

If these quantization values are divided by 2, the resulting
reconstructed image is usually nearly indistinguishable from the
source image.

Please provide any input by the 13th of February.

Cheers

Magnus

On 2014-09-04 16:33, RFC Errata System wrote:
> The following errata report has been submitted for RFC2435,
> "RTP Payload Format for JPEG-compressed Video".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=2435&eid=4094
> 
> --------------------------------------
> Type: Technical
> Reported by: Julius Richard Friedman <juliusfriedman@gmail.com>
> 
> Section: Appendix A
> 
> Original Text
> -------------
> /*
>  * Table K.1 from JPEG spec.
>  */
> static const int jpeg_luma_quantizer[64] = {
>         16, 11, 10, 16, 24, 40, 51, 61,
>         12, 12, 14, 19, 26, 58, 60, 55,
>         14, 13, 16, 24, 40, 57, 69, 56,
>         14, 17, 22, 29, 51, 87, 80, 62,
>         18, 22, 37, 56, 68, 109, 103, 77,
>         24, 35, 55, 64, 81, 104, 113, 92,
>         49, 64, 78, 87, 103, 121, 120, 101,
>         72, 92, 95, 98, 112, 100, 103, 99
> };
> 
> /*
>  * Table K.2 from JPEG spec.
>  */
> static const int jpeg_chroma_quantizer[64] = {
>         17, 18, 24, 47, 99, 99, 99, 99,
>         18, 21, 26, 66, 99, 99, 99, 99,
>         24, 26, 56, 99, 99, 99, 99, 99,
>         47, 66, 99, 99, 99, 99, 99, 99,
>         99, 99, 99, 99, 99, 99, 99, 99,
>         99, 99, 99, 99, 99, 99, 99, 99,
>         99, 99, 99, 99, 99, 99, 99, 99,
>         99, 99, 99, 99, 99, 99, 99, 99
> };
> 
> Corrected Text
> --------------
> /*
>  * Table K.1 from JPEG spec.
>  */
> static const int jpeg_luma_quantizer[64] = {
>            16, 11, 12, 14, 12, 10, 16, 14,
>            13, 14, 18, 17, 16, 19, 24, 40,
>            26, 24, 22, 22, 24, 49, 35, 37,
>            29, 40, 58, 51, 61, 60, 57, 51,
>            56, 55, 64, 72, 92, 78, 64, 68,
>            87, 69, 55, 56, 80, 109, 81, 87,
>            95, 98, 103, 104, 103, 62, 77, 113,
>            121, 112, 100, 120, 92, 101, 103, 99,
> };
> 
> /*
>  * Table K.2 from JPEG spec.
>  */
> static const int jpeg_chroma_quantizer[64] = {
>            17, 18, 18, 24, 21, 24, 47, 26,
>            26, 47, 99, 66, 56, 66, 99, 99,
>            99, 99, 99, 99, 99, 99, 99, 99,
>            99, 99, 99, 99, 99, 99, 99, 99,
>            99, 99, 99, 99, 99, 99, 99, 99,
>            99, 99, 99, 99, 99, 99, 99, 99,
>            99, 99, 99, 99, 99, 99, 99, 99,
>            99, 99, 99, 99, 99, 99, 99, 99
> };
> 
> Notes
> -----
> Luma and Chroma was not in Zig Zag order and Luma energy has been de-saturated.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC2435 (no draft string recorded)
> --------------------------------------
> Title               : RTP Payload Format for JPEG-compressed Video
> Publication Date    : October 1998
> Author(s)           : L. Berc, W. Fenner, R. Frederick, S. McCanne, P. Stewart
> Category            : PROPOSED STANDARD
> Source              : Audio/Video Transport
> Area                : Real-time Applications and Infrastructure
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Jan 29 05:00:49 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E9401A0364 for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 05:00:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P2KjzkpG2u2O for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 05:00:39 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C46631A0362 for <avt@ietf.org>; Thu, 29 Jan 2015 05:00:37 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-93-54ca2ef36556
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 3D.1C.04076.3FE2AC45; Thu, 29 Jan 2015 14:00:36 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.53) with Microsoft SMTP Server id 14.3.195.1; Thu, 29 Jan 2015 14:00:35 +0100
Message-ID: <54CA2EF3.2000108@ericsson.com>
Date: Thu, 29 Jan 2015 14:00:35 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: <alissa@cooperw.in>
References: <20140904145250.52B7118047E@rfc-editor.org>
In-Reply-To: <20140904145250.52B7118047E@rfc-editor.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrPLMWRmVeSWpSXmKPExsUyM+Jvje4XvVMhBrt/M1lMP/OX0eJlz0p2 i+MnmpgdmD2+PHnJ5LFz1l12jyVLfjIFMEdx2aSk5mSWpRbp2yVwZUz+9IO14LtPxbXug4wN jE3aXYycHBICJhLPd3UwQthiEhfurWfrYuTiEBI4wigxf+pEVghnOaNE26v9bCBVvALaEjtv /GcFsVkEVCVmtVxmBrHZBCwkbv5oBKsRFQiWWPz8KStEvaDEyZlPWEBsEQFxiZWNW8BsZgE9 iZ33m9hBbGEBR4kFMz8BzeEAWmYucfmmE0iYE2jkjXtbGSHKDSSOLJrDCmHLSzRvnQ22Vgjo nIamDtYJjIKzkGybhaRlFpKWBYzMqxhFi1OLi3PTjYz0Uosyk4uL8/P08lJLNjECQ/jglt9W OxgPPnc8xCjAwajEw2uw6GSIEGtiWXFl7iFGaQ4WJXFeO+NDIUIC6YklqdmpqQWpRfFFpTmp xYcYmTg4pRoYV4a8uezHGckYdmFyy8wpXV96Ncqs3TZ+kT9hIG7Z4DG7wWzHvfNW3jv2Pm7Z yszas6TOQHKvXM6FnUXVq2P+aWkqTPkRtf5oW6qd0uUJ87yk1pzvdvjv7ibwwHxB483w6r+u RTG/76s9z/CPq5G4zXJC94p4K1PXEVEb/rebK868Vpk8NYFHiaU4I9FQi7moOBEA4YVhMkIC AAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/SmuwwJBq9oyEkUbPthziAYm8lTA>
Cc: juliusfriedman@gmail.com, avt@ietf.org
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC2435 (4095)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 13:00:42 -0000

WG,

I would like to have your feedback on this errata.

It appears to me that the code is hard coded for three components. That
should be pretty evident for anyone reading the comments.

So from that perspective Julius is correct that the code was not taking
single component images into account. However, it is difficult to
determine the intention here.

I also wonder if the change is correct, especially why the first
occurrence of this line:

*p++ = 3;               /* number of components */

Is still equals to 3.

So WG is this Held for update or Reject.

Cheers

Magnus

On 2014-09-04 16:52, RFC Errata System wrote:
> The following errata report has been submitted for RFC2435,
> "RTP Payload Format for JPEG-compressed Video".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=2435&eid=4095
> 
> --------------------------------------
> Type: Technical
> Reported by: Julius Richard Friedman <juliusfriedman@gmail.com>
> 
> Section: Appendix B
> 
> Original Text
> -------------
> int MakeHeaders(u_char *p, int type, int w, int h, u_char *lqt,
>                 u_char *cqt, u_short dri)
> {
>         u_char *start = p;
> 
>         /* convert from blocks to pixels */
>         w <<= 3;
>         h <<= 3;
> 
> 
> 
> Berc, et. al.               Standards Track                    [Page 19]
>  
> RFC 2435              RTP Payload Format for JPEG           October 1998
> 
> 
>         *p++ = 0xff;
>         *p++ = 0xd8;            /* SOI */
> 
>         p = MakeQuantHeader(p, lqt, 0);
>         p = MakeQuantHeader(p, cqt, 1);
> 
>         if (dri != 0)
>                 p = MakeDRIHeader(p, dri);
> 
>         *p++ = 0xff;
>         *p++ = 0xc0;            /* SOF */
>         *p++ = 0;               /* length msb */
>         *p++ = 17;              /* length lsb */
>         *p++ = 8;               /* 8-bit precision */
>         *p++ = h >> 8;          /* height msb */
>         *p++ = h;               /* height lsb */
>         *p++ = w >> 8;          /* width msb */
>         *p++ = w;               /* wudth lsb */
>         *p++ = 3;               /* number of components */
>         *p++ = 0;               /* comp 0 */
>         if (type == 0)
>                 *p++ = 0x21;    /* hsamp = 2, vsamp = 1 */
>         else
>                 *p++ = 0x22;    /* hsamp = 2, vsamp = 2 */
>         *p++ = 0;               /* quant table 0 */
>         *p++ = 1;               /* comp 1 */
>         *p++ = 0x11;            /* hsamp = 1, vsamp = 1 */
>         *p++ = 1;               /* quant table 1 */
>         *p++ = 2;               /* comp 2 */
>         *p++ = 0x11;            /* hsamp = 1, vsamp = 1 */
>         *p++ = 1;               /* quant table 1 */
>         p = MakeHuffmanHeader(p, lum_dc_codelens,
>                               sizeof(lum_dc_codelens),
>                               lum_dc_symbols,
>                               sizeof(lum_dc_symbols), 0, 0);
>         p = MakeHuffmanHeader(p, lum_ac_codelens,
>                               sizeof(lum_ac_codelens),
>                               lum_ac_symbols,
>                               sizeof(lum_ac_symbols), 0, 1);
>         p = MakeHuffmanHeader(p, chm_dc_codelens,
>                               sizeof(chm_dc_codelens),
>                               chm_dc_symbols,
>                               sizeof(chm_dc_symbols), 1, 0);
>         p = MakeHuffmanHeader(p, chm_ac_codelens,
>                               sizeof(chm_ac_codelens),
>                               chm_ac_symbols,
>                               sizeof(chm_ac_symbols), 1, 1);
> 
> 
> 
> 
> Berc, et. al.               Standards Track                    [Page 20]
>  
> RFC 2435              RTP Payload Format for JPEG           October 1998
> 
> 
>         *p++ = 0xff;
>         *p++ = 0xda;            /* SOS */
>         *p++ = 0;               /* length msb */
>         *p++ = 12;              /* length lsb */
>         *p++ = 3;               /* 3 components */
>         *p++ = 0;               /* comp 0 */
>         *p++ = 0;               /* huffman table 0 */
>         *p++ = 1;               /* comp 1 */
>         *p++ = 0x11;            /* huffman table 1 */
>         *p++ = 2;               /* comp 2 */
>         *p++ = 0x11;            /* huffman table 1 */
>         *p++ = 0;               /* first DCT coeff */
>         *p++ = 63;              /* last DCT coeff */
>         *p++ = 0;               /* sucessive approx. */
> 
>         return (p - start);
> };
> 
> 
> Corrected Text
> --------------
> int MakeHeaders(u_char *p, int type, int w, int h, u_char *lqt,
>                 u_char *cqt, u_short dri)
> {
>         u_char *start = p;
> 
>         /* convert from blocks to pixels */
>         w <<= 3;
>         h <<= 3;
>         *p++ = 0xff;
>         *p++ = 0xd8;            /* SOI */
> 
>         p = MakeQuantHeader(p, lqt, 0);
>         if(cqt != NULL) p = MakeQuantHeader(p, cqt, 1);
> 
>         if (dri != 0)
>                 p = MakeDRIHeader(p, dri);
> 
>         *p++ = 0xff;
>         *p++ = 0xc0;            /* SOF */
>         *p++ = 0;               /* length msb */
>         *p++ = 17;              /* length lsb */
>         *p++ = 8;               /* 8-bit precision */
>         *p++ = h >> 8;          /* height msb */
>         *p++ = h;               /* height lsb */
>         *p++ = w >> 8;          /* width msb */
>         *p++ = w;               /* wudth lsb */
>         *p++ = 3;               /* number of components */
>         *p++ = 1;               /* comp 1 */
>         if (type == 0)
>                 *p++ = 0x21;    /* hsamp = 2, vsamp = 1 */
>         else
>                 *p++ = 0x22;    /* hsamp = 2, vsamp = 2 */
>         *p++ = 0;               /* quant table 0 */
>         *p++ = 1;               /* comp 1 */
>         *p++ = 0x11;            /* hsamp = 1, vsamp = 1 */
>         *p++ = 1;               /* quant table 1 */
>         *p++ = 2;               /* comp 2 */
>         *p++ = 0x11;            /* hsamp = 1, vsamp = 1 */
>         *p++ = 1;               /* quant table 1 */
>         p = MakeHuffmanHeader(p, lum_dc_codelens,
>                               sizeof(lum_dc_codelens),
>                               lum_dc_symbols,
>                               sizeof(lum_dc_symbols), 0, 0);
>         p = MakeHuffmanHeader(p, lum_ac_codelens,
>                               sizeof(lum_ac_codelens),
>                               lum_ac_symbols,
>                               sizeof(lum_ac_symbols), 0, 1);
>         if(cqt != NULL)
>         {
>         p = MakeHuffmanHeader(p, chm_dc_codelens,
>                               sizeof(chm_dc_codelens),
>                               chm_dc_symbols,
>                               sizeof(chm_dc_symbols), 1, 0);
>         p = MakeHuffmanHeader(p, chm_ac_codelens,
>                               sizeof(chm_ac_codelens),
>                               chm_ac_symbols,
>                               sizeof(chm_ac_symbols), 1, 1);
>        }
> 
> 
> 
> 
> Berc, et. al.               Standards Track                    [Page 20]
>  
> RFC 2435              RTP Payload Format for JPEG           October 1998
> 
> 
>         *p++ = 0xff;
>         *p++ = 0xda;            /* SOS */
>         *p++ = 0;               /* length msb */
>         *p++ = cqt != NULL ? 0x12 : 0x0b;/* length lsb */
>         *p++ = cqt != NULL ? 0x03 : 0x01;/* 3 components */
>         *p++ = 0;               /* comp 0 */
>         *p++ = 0;               /* huffman table 0 */
>         *p++ = 0x01;               /* comp 1 */
>         *p++ = cqt != NULL ? 0x11 : 0x00;/* huffman table 1 */
>         if(cqt != NULL) *p++ = 2;/* comp 2 */
>         *p++ = cqt != NULL ? 0x11 : 0x00;/* huffman table 1 */
>         *p++ = 0;               /* first DCT coeff */
>         *p++ = 63;              /* last DCT coeff */
>         *p++ = 0;               /* sucessive approx. */
> 
>         return (p - start);
> };
> 
> 
> Notes
> -----
> Did not take into account cases with only 1 component was used.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC2435 (no draft string recorded)
> --------------------------------------
> Title               : RTP Payload Format for JPEG-compressed Video
> Publication Date    : October 1998
> Author(s)           : L. Berc, W. Fenner, R. Frederick, S. McCanne, P. Stewart
> Category            : PROPOSED STANDARD
> Source              : Audio/Video Transport
> Area                : Real-time Applications and Infrastructure
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Jan 29 05:06:43 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB4291A0364 for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 05:06:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.601
X-Spam-Level: 
X-Spam-Status: No, score=-3.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dWy9q314DlUa for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 05:06:37 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8F2D1A0362 for <avt@ietf.org>; Thu, 29 Jan 2015 05:06:36 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-c0-54ca305aa9bc
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 55.4D.04076.A503AC45; Thu, 29 Jan 2015 14:06:35 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.56) with Microsoft SMTP Server id 14.3.195.1; Thu, 29 Jan 2015 14:06:34 +0100
Message-ID: <54CA305A.1040402@ericsson.com>
Date: Thu, 29 Jan 2015 14:06:34 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: <juliusfriedman@gmail.com>
References: <20140904152601.9343018001B@rfc-editor.org>
In-Reply-To: <20140904152601.9343018001B@rfc-editor.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrPLMWRmVeSWpSXmKPExsUyM+JvjW60wakQg61H2Symn/nLaPGyZyW7 xfETTcwOzB5fnrxk8tg56y67x5IlP5kCmKO4bFJSczLLUov07RK4Mh5tZy1YIF+x8OEs1gbG 02JdjJwcEgImEss/rGKCsMUkLtxbz9bFyMUhJHCEUWLPkbWMEM5yRoktS86DVfEKaEvcWrKA HcRmEVCV+HTmI5jNJmAhcfNHIxuILSoQLLH4+VNWiHpBiZMzn7CA2CICchK/Hs1iBLGZBdQl fv38wgxiCws4Stx4MAFsvpCAucSX7S/B4pxAM181v2OFqDeQOLJoDpQtL9G8dTYzRL22RENT B+sERsFZSNbNQtIyC0nLAkbmVYyixanFxbnpRkZ6qUWZycXF+Xl6eaklmxiBIXxwy2+rHYwH nzseYhTgYFTi4TVYdDJEiDWxrLgy9xCjNAeLkjivnfGhECGB9MSS1OzU1ILUovii0pzU4kOM TBycUg2MKWz8nLf+nf1VL7xxZum9X4kPlKcsTLg9mVt9c3ztw90SO98sqArP3cPNu+Kgt5go 18nYUpbJJwJMmyLc/h3/LyDUFf8jssp4VsI+x+khBezZmbd+K5rFacSLzVvavn7dui0bDgWy Pd7oWVM/L9b17aJoMeeEoE8Hv84+t+UdC6t0A8dFy3gBJZbijERDLeai4kQAu52AOEICAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/IDTdq2ZNR3wbeguAP_pCiMvqkRY>
Cc: avt@ietf.org
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC2435 (4096)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 13:06:42 -0000

Julius,

I would appreciate some clarification on the Errata. Is this an attempt
to raise a discussion around an improvement here, or something else?

Because without clarification this Errata will be rejected as makes no
correction.

/Magnus Westerlund


On 2014-09-04 17:26, RFC Errata System wrote:
> 
> The following errata report has been submitted for RFC2435,
> "RTP Payload Format for JPEG-compressed Video".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=2435&eid=4096
> 
> --------------------------------------
> Type: Technical
> Reported by: Julius Richard Friedman <juliusfriedman@gmail.com>
> 
> Section: Discussion
> 
> Original Text
> -------------
>  types  component samp. fact. samp. fact. table number
>          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>          |       |  1 (Y)  |     2     |     1     |     0     |
>          | 0, 64 |  2 (U)  |     1     |     1     |     1     |
>          |       |  3 (V)  |     1     |     1     |     1     |
>          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>          |       |  1 (Y)  |     2     |     2     |     0     |
>          | 1, 65 |  2 (U)  |     1     |     1     |     1     |
>          |       |  3 (V)  |     1     |     1     |     1     |
>          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> 
> Corrected Text
> --------------
> TO BE DETERMINED
> 
> Notes
> -----
> types  component samp. fact. samp. fact. table number
>         FROM StartOf Frame (0xFFC0)
> 
> Read Nf - Number of image components in frame
> 
> if(Nf > 1) 
> 
> Read Each Component
> 
>           0 1 2 3 4 5 6 7 
>          +-+-+-+-+-+-+-+-+
>          |   H   |   V   |
>          +-+-+-+-+-+-+-+-+
> 
> H: Horizontal sampling factor â€“ Specifies the relationship between the component horizontal dimension
> and maximum image dimension X (see Jpeg Spec A.1.1); also specifies the number of horizontal data units of component
> Ci in each MCU, when more than one component is encoded in a scan.
> Vi: Vertical sampling factor â€“ Specifies the relationship between the component vertical dimension and
> maximum image dimension Y (see Jpeg Spec A.1.1); also specifies the number of vertical data units of component Ci in
> each MCU, when more than one component is encoded in a scan.
> Tqi: Implied from the position in parsing
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC2435 (no draft string recorded)
> --------------------------------------
> Title               : RTP Payload Format for JPEG-compressed Video
> Publication Date    : October 1998
> Author(s)           : L. Berc, W. Fenner, R. Frederick, S. McCanne, P. Stewart
> Category            : PROPOSED STANDARD
> Source              : Audio/Video Transport
> Area                : Real-time Applications and Infrastructure
> Stream              : IETF
> Verifying Party     : IESG
> 
> 
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> 

-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Jan 29 05:11:25 2015
Return-Path: <ron.frederick@bluecoat.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08B3D1A0371 for <avt@ietfa.amsl.com>; Wed, 28 Jan 2015 12:38:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5knMURUFaH7s for <avt@ietfa.amsl.com>; Wed, 28 Jan 2015 12:38:13 -0800 (PST)
Received: from plsvl-mailgw-02.bluecoat.com (plsvl-mailgw-02.bluecoat.com [199.91.133.12]) by ietfa.amsl.com (Postfix) with ESMTP id 785891A0389 for <avt@ietf.org>; Wed, 28 Jan 2015 12:38:13 -0800 (PST)
Received: from pwsvl-exchts-03.internal.cacheflow.com (pwsvl-exchts-03.bluecoat.com [10.2.2.160]) by plsvl-mailgw-02.bluecoat.com (Postfix) with ESMTP id 4698F200BF; Wed, 28 Jan 2015 12:38:13 -0800 (PST)
Received: from pwsvl-excmbx-05.internal.cacheflow.com ([fe80::f848:d461:9aa9:59a8]) by pwsvl-exchts-03.internal.cacheflow.com ([fe80::1ded:e21:ed06:fdc6%11]) with mapi id 14.03.0123.003; Wed, 28 Jan 2015 12:38:13 -0800
From: "Frederick, Ron" <ron.frederick@bluecoat.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: [AVTCORE] [Technical Errata Reported] RFC2435 (4097)
Thread-Index: AQHQOxTJeHuTKICix0ivevGjR39yvZzWhJyA
Date: Wed, 28 Jan 2015 20:38:11 +0000
Message-ID: <D6E0A685-C106-42D4-BEF8-8B6BD664452E@bluecoat.com>
References: <20140904164839.0F554180450@rfc-editor.org> <54C9048F.1000509@ericsson.com>
In-Reply-To: <54C9048F.1000509@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.2.2.106]
Content-Type: multipart/alternative; boundary="_000_D6E0A685C10642D4BEF88B6BD664452Ebluecoatcom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/2ddFYes-Bfc8XaqecOfS5PA6uZg>
X-Mailman-Approved-At: Thu, 29 Jan 2015 05:11:23 -0800
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC2435 (4097)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 20:38:16 -0000

--_000_D6E0A685C10642D4BEF88B6BD664452Ebluecoatcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

I agree with this. Here are some other issues:

- The =93Original text=94 is actually wrong here. Both the width and height=
 in the original text have a maximum of 2040 pixels. I=92m guessing that th=
e intent was to update this to 65535 for both width & height in the correct=
ed text, but that would have been wrong as well. If I understand the propos=
al, the maximum supported value here would become 255*256, or 65280 pixels.

- I don=92t understand how the receiving system is supposed to know whether=
 the divisor is 8 or 256. Perhaps the text in the =93Notes=94 was intended =
to somehow deal with this, but what=92s proposed there doesn=92t make sense=
 to me. I also don=92t see how this could be done in a manner which is back=
ward compatible with existing clients.

- Using a larger divisor also has another problem. It would be impossible t=
o represent image widths or heights greater than 2040 pixels that were not =
a multiple of 8. While we already have an issue with not being able to repr=
esent non-multiples of 8 in the current spec, that was done with the expect=
ation that the JPEG block size would generally constrain images to 8x8, 16x=
8, or 16x16 size blocks, so that was not a strong requirement. Requiring la=
rger sizes to always be a multiple of 256 seems like it would be much more =
problematic, and I think we need a better solution for that.

On Jan 28, 2015, at 7:47 AM, Magnus Westerlund <magnus.westerlund@ericsson.=
com<mailto:magnus.westerlund@ericsson.com>> wrote:

WG,

My proposal is that this Errata is "Rejected" based on that its section
of change does not contain any change. And the notes part proposed
changed is a redefinition of a field, i.e. something that would require
a replacement RFC to change.

Please provide any comments by the 12th of February.

Cheers

Magnus Westerlund
WG chair


On 2014-09-04 18:48, RFC Errata System wrote:
The following errata report has been submitted for RFC2435,
"RTP Payload Format for JPEG-compressed Video".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3D2435&eid=3D4097

--------------------------------------
Type: Technical
Reported by: Julius Richard Friedman <juliusfriedman@gmail.com>

Section: 3.1.5

Original Text
-------------
3.1.5.  Width: 8 bits

  This field encodes the width of the image in 8-pixel multiples (e.g.,
  a width of 40 denotes an image 320 pixels wide).  The maximum width
  is 2040 pixels.

3.1.6.  Height: 8 bits

  This field encodes the height of the image in 8-pixel multiples
  (e.g., a height of 30 denotes an image 240 pixels tall). When
  encoding interlaced video, this is the height of a video field, since
  fields are individually JPEG encoded. The maximum height is 65535
  pixels.

Corrected Text
--------------
3.1.5.  Width: 8 bits

  This field encodes the width of the image in 8-pixel multiples (e.g.,
  a width of 40 denotes an image 320 pixels wide).  The maximum width
  is 2040 pixels.

3.1.6.  Height: 8 bits

  This field encodes the height of the image in 8-pixel multiples
  (e.g., a height of 30 denotes an image 240 pixels tall). When
  encoding interlaced video, this is the height of a video field, since
  fields are individually JPEG encoded. The maximum height is 65535
  pixels.

Notes
-----
Use a divisor of 256 to determine the height, where 8 / 256 =3D 32.

Ensure FragmentOffset does not exceed 2^24, if it does then use 2^24 - valu=
e)

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary.

--------------------------------------
RFC2435 (no draft string recorded)
--------------------------------------
Title               : RTP Payload Format for JPEG-compressed Video
Publication Date    : October 1998
Author(s)           : L. Berc, W. Fenner, R. Frederick, S. McCanne, P. Stew=
art
Category            : PROPOSED STANDARD
Source              : Audio/Video Transport
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG
--
Ron Frederick
ronf@bluecoat.com<mailto:ronf@bluecoat.com>




--_000_D6E0A685C10642D4BEF88B6BD664452Ebluecoatcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <96277880ED0D924A8D2F1B882F91C16D@bluecoat.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;" class=3D"">
<div>I agree with this. Here are some other issues:</div>
<div><br class=3D"">
</div>
<div>- The =93Original text=94 is actually wrong here. Both the width and h=
eight in the original text have a maximum of 2040 pixels. I=92m guessing th=
at the intent was to update this to 65535 for both width &amp; height in th=
e corrected text, but that would have been
 wrong as well. If I understand the proposal, the maximum supported value h=
ere would become 255*256, or 65280 pixels.</div>
<div><br class=3D"">
</div>
<div>- I don=92t understand how the receiving system is supposed to know wh=
ether the divisor is 8 or 256. Perhaps the text in the =93Notes=94 was inte=
nded to somehow deal with this, but what=92s proposed there doesn=92t make =
sense to me. I also don=92t see how this could
 be done in a manner which is backward compatible with existing clients.</d=
iv>
<div><br class=3D"">
</div>
<div>- Using a larger divisor also has another problem. It would be impossi=
ble to represent image widths or heights greater than 2040 pixels that were=
 not a multiple of 8. While we already have an issue with not being able to=
 represent non-multiples of 8 in
 the current spec, that was done with the expectation that the JPEG block s=
ize would generally constrain images to 8x8, 16x8, or 16x16 size blocks, so=
 that was not a strong requirement. Requiring larger sizes to always be a m=
ultiple of 256 seems like it would
 be much more problematic, and I think we need a better solution for that.<=
/div>
<div><br class=3D"">
</div>
<div>On Jan 28, 2015, at 7:47 AM, Magnus Westerlund &lt;<a href=3D"mailto:m=
agnus.westerlund@ericsson.com" class=3D"">magnus.westerlund@ericsson.com</a=
>&gt; wrote:<br class=3D"">
<blockquote type=3D"cite" class=3D""><br class=3D"Apple-interchange-newline=
">
<div class=3D"">WG,<br class=3D"">
<br class=3D"">
My proposal is that this Errata is &quot;Rejected&quot; based on that its s=
ection<br class=3D"">
of change does not contain any change. And the notes part proposed<br class=
=3D"">
changed is a redefinition of a field, i.e. something that would require<br =
class=3D"">
a replacement RFC to change.<br class=3D"">
<br class=3D"">
Please provide any comments by the 12th of February.<br class=3D"">
<br class=3D"">
Cheers<br class=3D"">
<br class=3D"">
Magnus Westerlund<br class=3D"">
WG chair<br class=3D"">
<br class=3D"">
<br class=3D"">
On 2014-09-04 18:48, RFC Errata System wrote:<br class=3D"">
<blockquote type=3D"cite" class=3D"">The following errata report has been s=
ubmitted for RFC2435,<br class=3D"">
&quot;RTP Payload Format for JPEG-compressed Video&quot;.<br class=3D"">
<br class=3D"">
--------------------------------------<br class=3D"">
You may review the report below and at:<br class=3D"">
<a href=3D"http://www.rfc-editor.org/errata_search.php?rfc=3D2435&amp;eid=
=3D4097" class=3D"">http://www.rfc-editor.org/errata_search.php?rfc=3D2435&=
amp;eid=3D4097</a><br class=3D"">
<br class=3D"">
--------------------------------------<br class=3D"">
Type: Technical<br class=3D"">
Reported by: Julius Richard Friedman &lt;juliusfriedman@gmail.com&gt;<br cl=
ass=3D"">
<br class=3D"">
Section: 3.1.5<br class=3D"">
<br class=3D"">
Original Text<br class=3D"">
-------------<br class=3D"">
3.1.5. &nbsp;Width: 8 bits<br class=3D"">
<br class=3D"">
&nbsp;&nbsp;This field encodes the width of the image in 8-pixel multiples =
(e.g.,<br class=3D"">
&nbsp;&nbsp;a width of 40 denotes an image 320 pixels wide). &nbsp;The maxi=
mum width<br class=3D"">
&nbsp;&nbsp;is 2040 pixels.<br class=3D"">
<br class=3D"">
3.1.6. &nbsp;Height: 8 bits<br class=3D"">
<br class=3D"">
&nbsp;&nbsp;This field encodes the height of the image in 8-pixel multiples=
<br class=3D"">
&nbsp;&nbsp;(e.g., a height of 30 denotes an image 240 pixels tall). When<b=
r class=3D"">
&nbsp;&nbsp;encoding interlaced video, this is the height of a video field,=
 since<br class=3D"">
&nbsp;&nbsp;fields are individually JPEG encoded. The maximum height is 655=
35<br class=3D"">
&nbsp;&nbsp;pixels.<br class=3D"">
<br class=3D"">
Corrected Text<br class=3D"">
--------------<br class=3D"">
3.1.5. &nbsp;Width: 8 bits<br class=3D"">
<br class=3D"">
&nbsp;&nbsp;This field encodes the width of the image in 8-pixel multiples =
(e.g.,<br class=3D"">
&nbsp;&nbsp;a width of 40 denotes an image 320 pixels wide). &nbsp;The maxi=
mum width<br class=3D"">
&nbsp;&nbsp;is 2040 pixels.<br class=3D"">
<br class=3D"">
3.1.6. &nbsp;Height: 8 bits<br class=3D"">
<br class=3D"">
&nbsp;&nbsp;This field encodes the height of the image in 8-pixel multiples=
<br class=3D"">
&nbsp;&nbsp;(e.g., a height of 30 denotes an image 240 pixels tall). When<b=
r class=3D"">
&nbsp;&nbsp;encoding interlaced video, this is the height of a video field,=
 since<br class=3D"">
&nbsp;&nbsp;fields are individually JPEG encoded. The maximum height is 655=
35<br class=3D"">
&nbsp;&nbsp;pixels.<br class=3D"">
<br class=3D"">
Notes<br class=3D"">
-----<br class=3D"">
Use a divisor of 256 to determine the height, where 8 / 256 =3D 32.<br clas=
s=3D"">
<br class=3D"">
Ensure FragmentOffset does not exceed 2^24, if it does then use 2^24 - valu=
e)<br class=3D"">
<br class=3D"">
Instructions:<br class=3D"">
-------------<br class=3D"">
This erratum is currently posted as &quot;Reported&quot;. If necessary, ple=
ase<br class=3D"">
use &quot;Reply All&quot; to discuss whether it should be verified or<br cl=
ass=3D"">
rejected. When a decision is reached, the verifying party (IESG)<br class=
=3D"">
can log in to change the status and edit the report, if necessary. <br clas=
s=3D"">
<br class=3D"">
--------------------------------------<br class=3D"">
RFC2435 (no draft string recorded)<br class=3D"">
--------------------------------------<br class=3D"">
Title &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;: RTP Payload Format for JPEG-compressed Video<br class=3D""=
>
Publication Date &nbsp;&nbsp;&nbsp;: October 1998<br class=3D"">
Author(s) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: L. =
Berc, W. Fenner, R. Frederick, S. McCanne, P. Stewart<br class=3D"">
Category &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
: PROPOSED STANDARD<br class=3D"">
Source &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;: Audio/Video Transport<br class=3D"">
Area &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;: Real-time Applications and Infrastructure<br class=3D=
"">
Stream &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;: IETF<br class=3D"">
Verifying Party &nbsp;&nbsp;&nbsp;&nbsp;: IESG<br class=3D"">
</blockquote>
</div>
</blockquote>
</div>
<div apple-content-edited=3D"true" class=3D""><span class=3D"Apple-style-sp=
an" style=3D"border-collapse: separate; border-spacing: 0px;">
<div class=3D"">--&nbsp;</div>
<div class=3D"">Ron Frederick</div>
<div class=3D""><a href=3D"mailto:ronf@bluecoat.com" class=3D"">ronf@blueco=
at.com</a></div>
<div class=3D""><br class=3D"">
</div>
</span><br class=3D"Apple-interchange-newline">
</div>
<br class=3D"">
</body>
</html>

--_000_D6E0A685C10642D4BEF88B6BD664452Ebluecoatcom_--


From nobody Thu Jan 29 05:38:07 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B51D41A0397; Thu, 29 Jan 2015 05:37:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ESVE9i46gRW9; Thu, 29 Jan 2015 05:37:55 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B83C11A037E; Thu, 29 Jan 2015 05:37:54 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-1e-54ca37b08969
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id D5.A2.04076.0B73AC45; Thu, 29 Jan 2015 14:37:52 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.83) with Microsoft SMTP Server id 14.3.195.1; Thu, 29 Jan 2015 14:37:52 +0100
Message-ID: <54CA37B0.6060306@ericsson.com>
Date: Thu, 29 Jan 2015 14:37:52 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Julius Friedman <juliusfriedman@gmail.com>, <mmusic@ietf.org>, <avt@ietf.org>
References: <CACFvNHVFUe7jHEK00ja3Vppi5GYeKptOuVPi97HrYU3DdiyLCA@mail.gmail.com>
In-Reply-To: <CACFvNHVFUe7jHEK00ja3Vppi5GYeKptOuVPi97HrYU3DdiyLCA@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprDLMWRmVeSWpSXmKPExsUyM+Jvje4G81MhBlPWW1m87FnJbnH8RBOz xdTlj1kcmD12zrrL7rFkyU+mAKYoLpuU1JzMstQifbsEroydm7awFTQJVcxa/IKxgbGXr4uR g0NCwERi72+/LkZOIFNM4sK99WxdjFwcQgJHGCUmHOmDcpYzSjTfX88OUsUroC0x+dlEJhCb RUBV4uHHK2A2m4CFxM0fjWwgtqhAsMTi509ZIeoFJU7OfMICskwEKL7kRxxIWFhAUaLhyERG EFtIIEBi99lXrCAlnAKBEkdmRIOEmQUMJI4smsMKYctLNG+dzQxRri3R0NTBOoFRYBaSBbOQ tMxC0rKAkXkVo2hxanFxbrqRkV5qUWZycXF+nl5easkmRmBwHtzy22oH48HnjocYBTgYlXh4 DRadDBFiTSwrrsw9xCjNwaIkzmtnfChESCA9sSQ1OzW1ILUovqg0J7X4ECMTB6dUA2Myw+VL l1m4NnGJrDFoEzx961p0sZKrytp42cD2sAyVu+ceHEg6dmX5lf8ZHmLCx++Gbe5Z+sdtb2/U ee3PHqf1Ol9qBp2Rcb2tIPTMY5I796wAnUUXdr7zP3ugUHmHl36lV4eC0THZ1B3//5w0i3jg 33mYU6/JZaGvY8aF0IVCt+KCVNq3bVFiKc5INNRiLipOBAA6HUZOLwIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/5F72w2t3_9WsHUFVyp5SijAkQgk>
Subject: Re: [AVTCORE] On RFC2326
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 13:37:57 -0000

On 2015-01-18 20:33, Julius Friedman wrote:
> Unfortunately I have more information which I have found to be
> contradictory and possibly erratum.
> 
> Quite Succinctly,
> 
> "
> 
> 
>       10.7 <https://tools.ietf.org/html/rfc2326#section-10.7> TEARDOWN
> 
> 
> 
>    The TEARDOWN request stops the stream delivery for the given URI,
>    freeing the resources associated with it. If the URI is the
>    presentation URI for this presentation, any RTSP session identifier
>    associated with the session is no longer valid. Unless all transport
>    parameters are defined by the session description, a SETUP request
>    has to be issued before the session can be played again.
> 
> "
> 
> 
> However earlier in the document.
> 
> 
> "
> 
> 
>       10.4 <https://tools.ietf.org/html/rfc2326#section-10.4> SETUP
> 
> 
>       ....
> 
> 
> 
> The server generates session identifiers in response to SETUP
>    requests. If a SETUP request to a server includes a session
>    identifier, the server MUST bundle this setup request into the
> 
>    existing session or return error "459 Aggregate Operation Not
>    Allowed" (see Section 11.3.10 <https://tools.ietf.org/html/rfc2326#section-11.3.10>).
> 
> "
> 
> 
> If a users obtains a session Id related to an aggregate controlled
media and only one of the sub sessions received a "TEARDOWN" then the
RFC makes the server incorrectly remove the SessionId which is still
being used for the other sub-sessions.
> 
> 
> 
> The draft doesn't do any better in making this clearer IMHO.
> 

What I can see
https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc2326bis/ in
Section 13.7.1 is clear on this. If you are disagreeing that this issue
is resolved. Please be explicit in what way it isn't resolved.

cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Jan 29 18:28:44 2015
Return-Path: <worley@alum.mit.edu>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA881A88EA for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 18:28:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zlB93OddGr_2 for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 18:28:42 -0800 (PST)
Received: from resqmta-po-11v.sys.comcast.net (resqmta-po-11v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:170]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC8D21A88E8 for <avt@ietf.org>; Thu, 29 Jan 2015 18:28:41 -0800 (PST)
Received: from resomta-po-10v.sys.comcast.net ([96.114.154.234]) by resqmta-po-11v.sys.comcast.net with comcast id m2TY1p00453iAfU012UhEh; Fri, 30 Jan 2015 02:28:41 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-po-10v.sys.comcast.net with comcast id m2Uf1p00Y1KKtkw012Ugsa; Fri, 30 Jan 2015 02:28:41 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id t0U2Sdp7022376; Thu, 29 Jan 2015 21:28:39 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id t0U2Sced022373; Thu, 29 Jan 2015 21:28:38 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
In-Reply-To: <54CA2EF3.2000108@ericsson.com> (magnus.westerlund@ericsson.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Thu, 29 Jan 2015 21:28:38 -0500
Message-ID: <87vbjpgfxl.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1422584921; bh=w6pReOtWCt42qrL6xBzSc/QiriQnReOIvtc+mfMrz7g=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=HcUvNOvPvCR/0Y3aCsKZkKgzf86xSMQ0I1PyiDnKvL9FaB0CuXGtOJKhqn7YO1F6j dvzJ+B1lLlhznqToL6F2pcQ8/eau8VJMDXwZJYiwUZzvC0zipxxGMzaQH5Nsmdroa7 zY5m+n9Ki0BF8vDyPLJHX00bCmRQUjQKBs8akoLxzE5NU54P5nCCbovvTuWwJKPRgf 9TpQq+0L/85qNuod9Y9gSAZ3jgi1XcQoAp+QW8kx+/bml7GBI7dDlMllQQ+XkeXgxc 2UQbs491cn0JAIH1RmYzP6ifo+Zbpc5wzaJBN2UNyqWcb/qGS1MDEJ+3q6ADBi6XIl vxnKJe0aFDOXw==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/ZYvvIJ5_aToypvW_DIHIz0dmr1U>
Cc: juliusfriedman@gmail.com, avt@ietf.org
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC2435 (4095)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 02:28:43 -0000

Magnus Westerlund <magnus.westerlund@ericsson.com> writes:
> I would like to have your feedback on this errata.
>
> It appears to me that the code is hard coded for three components. That
> should be pretty evident for anyone reading the comments.
>
> So from that perspective Julius is correct that the code was not taking
> single component images into account. However, it is difficult to
> determine the intention here.

The code change in the erratum is:

    --- says	2015-01-29 21:21:01.578501194 -0500
    +++ should-say	2015-01-29 21:20:32.139678733 -0500
    @@ -1,4 +1,4 @@
    -Section Appendix B says:
    +It should say:

     int MakeHeaders(u_char *p, int type, int w, int h, u_char *lqt,
                     u_char *cqt, u_short dri)
    @@ -12,7 +12,7 @@
             *p++ = 0xd8;            /* SOI */

             p = MakeQuantHeader(p, lqt, 0);
    -        p = MakeQuantHeader(p, cqt, 1);
    +        if(cqt != NULL) p = MakeQuantHeader(p, cqt, 1);

             if (dri != 0)
                     p = MakeDRIHeader(p, dri);
    @@ -27,7 +27,7 @@
             *p++ = w >> 8;          /* width msb */
             *p++ = w;               /* wudth lsb */
             *p++ = 3;               /* number of components */
    -        *p++ = 0;               /* comp 0 */
    +        *p++ = 1;               /* comp 1 */
             if (type == 0)
                     *p++ = 0x21;    /* hsamp = 2, vsamp = 1 */
             else
    @@ -47,6 +47,8 @@
                                   sizeof(lum_ac_codelens),
                                   lum_ac_symbols,
                                   sizeof(lum_ac_symbols), 0, 1);
    +        if(cqt != NULL)
    +        {
             p = MakeHuffmanHeader(p, chm_dc_codelens,
                                   sizeof(chm_dc_codelens),
                                   chm_dc_symbols,
    @@ -55,6 +57,7 @@
                                   sizeof(chm_ac_codelens),
                                   chm_ac_symbols,
                                   sizeof(chm_ac_symbols), 1, 1);
    +       }



    @@ -67,14 +70,14 @@
             *p++ = 0xff;
             *p++ = 0xda;            /* SOS */
             *p++ = 0;               /* length msb */
    -        *p++ = 12;              /* length lsb */
    -        *p++ = 3;               /* 3 components */
    +        *p++ = cqt != NULL ? 0x12 : 0x0b;/* length lsb */
    +        *p++ = cqt != NULL ? 0x03 : 0x01;/* 3 components */
             *p++ = 0;               /* comp 0 */
             *p++ = 0;               /* huffman table 0 */
    -        *p++ = 1;               /* comp 1 */
    -        *p++ = 0x11;            /* huffman table 1 */
    -        *p++ = 2;               /* comp 2 */
    -        *p++ = 0x11;            /* huffman table 1 */
    +        *p++ = 0x01;               /* comp 1 */
    +        *p++ = cqt != NULL ? 0x11 : 0x00;/* huffman table 1 */
    +        if(cqt != NULL) *p++ = 2;/* comp 2 */
    +        *p++ = cqt != NULL ? 0x11 : 0x00;/* huffman table 1 */
             *p++ = 0;               /* first DCT coeff */
             *p++ = 63;              /* last DCT coeff */
             *p++ = 0;               /* sucessive approx. */

I don't understand the code, but it appears that the "should-say" code is
intended to work as the "says" code works when cqt is not NULL.

However, this change is always operative:

    -        *p++ = 0;               /* comp 0 */
    +        *p++ = 1;               /* comp 1 */

And this change is peculiar, in that the first character assigned to p
changes from 12 to a choice between 18 (0x12) and 11 (0xB).  I wonder if
0x12 is intended to be 12?

    -        *p++ = 12;              /* length lsb */
    -        *p++ = 3;               /* 3 components */
    +        *p++ = cqt != NULL ? 0x12 : 0x0b;/* length lsb */
    +        *p++ = cqt != NULL ? 0x03 : 0x01;/* 3 components */

Dale


From nobody Thu Jan 29 18:34:14 2015
Return-Path: <worley@alum.mit.edu>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B5521A88E8 for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 18:34:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HaVEOPnKaBZr for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 18:34:11 -0800 (PST)
Received: from resqmta-po-08v.sys.comcast.net (resqmta-po-08v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:167]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D08801A88E1 for <avt@ietf.org>; Thu, 29 Jan 2015 18:34:11 -0800 (PST)
Received: from resomta-po-02v.sys.comcast.net ([96.114.154.226]) by resqmta-po-08v.sys.comcast.net with comcast id m2Zx1p0034tLnxL012aB2c; Fri, 30 Jan 2015 02:34:11 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-po-02v.sys.comcast.net with comcast id m2a91p00Y1KKtkw012aA6q; Fri, 30 Jan 2015 02:34:11 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id t0U2Y9Of022993; Thu, 29 Jan 2015 21:34:09 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id t0U2Y95n022990; Thu, 29 Jan 2015 21:34:09 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
In-Reply-To: <54CA2B9C.2090208@ericsson.com> (magnus.westerlund@ericsson.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Thu, 29 Jan 2015 21:34:09 -0500
Message-ID: <87sietgfoe.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1422585251; bh=M1ddrEkfWaKfriLGEakvii4TAYfKbJa4Tu0SYCsZztI=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=nh4GTGfi4FZQ7XdJbpVbTnWzRdpy6lsXBGV/ppawDtmxyz68se0JPIhKTvz3M+lmH 4Z6F6bdjnXfvu4rWTE2WHpG/cENuJSSNowmqru4DtrJ9wT2kak8229FU5KGl0VkGee ItzOzqXXxp01VVHYsQ9zdRU18BD2FUsa2bW+4g5TFUun4jdV9g0vHiEX77XMPW6tDF Vp+TWWMs9zQQiEjVWt6HtB1ptatr7Sv775J5KXQzfMd0meJO2cWSBH/8Dog5XqRmB8 Poqz/hgMs4318EChhG4VJI6ksgntcSlDEaTWuTnHM/h1M/fOT0B7I7vEor74xlK7ZY CjX6jlKzJBLLA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/UkEQhCN8PcDDO-eNk5zJ88LXE7k>
Cc: juliusfriedman@gmail.com, avt@ietf.org
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC2435 (4094)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 02:34:12 -0000

Magnus Westerlund <magnus.westerlund@ericsson.com> writes:
> I need your input on this Errata. Should it be held for document update
> or Rejected?

It's difficult to say because it's not clear (at least to me) what the
erratum is intended to do.  I would need to see a more detailed
explanation of the error the erratum is intended to correct.

Dale


From nobody Thu Jan 29 18:36:02 2015
Return-Path: <juliusfriedman@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5AA61A88E8 for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 18:35:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3p6UlN40lPud for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 18:35:56 -0800 (PST)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69A4A1A88E1 for <avt@ietf.org>; Thu, 29 Jan 2015 18:35:56 -0800 (PST)
Received: by mail-pa0-f53.google.com with SMTP id kx10so46290976pab.12 for <avt@ietf.org>; Thu, 29 Jan 2015 18:35:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=edYIxD2W2zd/rKBaAR8sn1M0wDIsaUmLkt86LZQna3g=; b=ecBanAOXtrO9hAEJ1btzXRI9JIB9ha3VEZBz2sRD8xZWbAhAEiqdkx4oe1yiR1C04W SiwbzW09sT/VR8P21ziN/qRyJ5ojAdJXXijLpDJhhIp/TTmJs3PfOqvjlNys6xq8JL2F AhlOaLxu8JFZ4DqTTwdAbwmXrQyKQ+oOunok4pR/QoghJdm0SrVpRoWSlJvG2pqEbXuc sbC4mDdnjtoxdLyIeHtFPBtsOeDmC/XGdmaWGWDywC24J4PtKTuhJ48lt0uSP3lNzg1O ouChTYTWETBy+81g65+j4SOdbxLB8hXRsHsx1JvYbguLW4o5f/wjrFGadhYjlF6uP4Ry R+wQ==
MIME-Version: 1.0
X-Received: by 10.68.236.67 with SMTP id us3mr5173522pbc.121.1422585355655; Thu, 29 Jan 2015 18:35:55 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Thu, 29 Jan 2015 18:35:55 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Thu, 29 Jan 2015 18:35:55 -0800 (PST)
In-Reply-To: <87vbjpgfxl.fsf@hobgoblin.ariadne.com>
References: <54CA2EF3.2000108@ericsson.com> <87vbjpgfxl.fsf@hobgoblin.ariadne.com>
Date: Thu, 29 Jan 2015 21:35:55 -0500
Message-ID: <CACFvNHW5F_fHYiF_p4h2Ot4=WO7gVjUBsZGNFVvm0R54U2RnXw@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary=047d7b2e11b1c960ed050dd57667
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/xeJGIEp6jPdJQLYeKJ4aPPkJrKk>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC2435 (4095)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 02:36:00 -0000

--047d7b2e11b1c960ed050dd57667
Content-Type: text/plain; charset=UTF-8

Magnus has my input,   I will also include it here in case I was supposed
to.

Here is my input and explanation for 4095.

The implementation I have is similar to the annex code I changed and uses
the number of components corresponding to those from the jpeg SOS marker.

The functionality was already hardcoded for two tables and the case of 1
table all the data probably belongs to only the luma table but the table
class decided that.

The function definition could be changed to give an array of each
components but I believe the maximum number of components is 4 anyway and
because its a 4 bit value i ignored it.

This goes back to being compatible and why I opted to change the annex the
way I did.

Cases of 0 and 1 table are now handled.

Cases of 2 tables were previously handled (although if they use different
sizes tables without precision the given code will also fail although im
not sure this is typically seen as a table usually has either 64 or 128
octets and the same number for each other table generated. )

Cases of 3 also now handled. (With th above notion in mind about all tables
being the same length or requiring precision)

Cases of 4 tables should also be handled in my opinion if they are not ;
but you can't have a value 4 there...

I believe the code used the three tables to determine if there were any
more remaining but I may have omitted that code from the erratum.

In short it may be beneficial to change the function definition to give
those components and their lengths; if that decision is made the result
will be easier to follow but I also defer there for your opinion.

There is also a problem using the given standard table on progressive
encoded images.

I have answered another question related to this here which may make more
sense.

http://stackoverflow.com/questions/25662584/how-to-convert-a-jpeg-444-ycbcr-to-422-ycbcr/25676532#25676532

My code is which is working with this method is @
http://net7mma.codeplex.com/SourceControl/latest#RtspServer/MediaTypes/RFC2435Media.cs

The project also has a number of jpeg images to test on which fail in the
annex code, two of which are argb and cmyk.

The latter two would require some custom sdp and the header or other
informat to be given explicitly there and it should be noted that I am not
arguing for those formats, just the ones allowed by the baseline
specification which includes progressive.

I do however feel that any updates to the document should allow for any
jpeg, onvif does this differently and it may work looking at how they do it
to ensure compatible implementations are possible.

http://www.onvif.org/specs/stream/ONVIF-Streaming-Spec-v210.pdf

Thanks,
Julius
Magnus Westerlund <magnus.westerlund@ericsson.com> writes:
> I would like to have your feedback on this errata.
>
> It appears to me that the code is hard coded for three components. That
> should be pretty evident for anyone reading the comments.
>
> So from that perspective Julius is correct that the code was not taking
> single component images into account. However, it is difficult to
> determine the intention here.

The code change in the erratum is:

    --- says    2015-01-29 21:21:01.578501194 -0500
    +++ should-say      2015-01-29 21:20:32.139678733 -0500
    @@ -1,4 +1,4 @@
    -Section Appendix B says:
    +It should say:

     int MakeHeaders(u_char *p, int type, int w, int h, u_char *lqt,
                     u_char *cqt, u_short dri)
    @@ -12,7 +12,7 @@
             *p++ = 0xd8;            /* SOI */

             p = MakeQuantHeader(p, lqt, 0);
    -        p = MakeQuantHeader(p, cqt, 1);
    +        if(cqt != NULL) p = MakeQuantHeader(p, cqt, 1);

             if (dri != 0)
                     p = MakeDRIHeader(p, dri);
    @@ -27,7 +27,7 @@
             *p++ = w >> 8;          /* width msb */
             *p++ = w;               /* wudth lsb */
             *p++ = 3;               /* number of components */
    -        *p++ = 0;               /* comp 0 */
    +        *p++ = 1;               /* comp 1 */
             if (type == 0)
                     *p++ = 0x21;    /* hsamp = 2, vsamp = 1 */
             else
    @@ -47,6 +47,8 @@
                                   sizeof(lum_ac_codelens),
                                   lum_ac_symbols,
                                   sizeof(lum_ac_symbols), 0, 1);
    +        if(cqt != NULL)
    +        {
             p = MakeHuffmanHeader(p, chm_dc_codelens,
                                   sizeof(chm_dc_codelens),
                                   chm_dc_symbols,
    @@ -55,6 +57,7 @@
                                   sizeof(chm_ac_codelens),
                                   chm_ac_symbols,
                                   sizeof(chm_ac_symbols), 1, 1);
    +       }



    @@ -67,14 +70,14 @@
             *p++ = 0xff;
             *p++ = 0xda;            /* SOS */
             *p++ = 0;               /* length msb */
    -        *p++ = 12;              /* length lsb */
    -        *p++ = 3;               /* 3 components */
    +        *p++ = cqt != NULL ? 0x12 : 0x0b;/* length lsb */
    +        *p++ = cqt != NULL ? 0x03 : 0x01;/* 3 components */
             *p++ = 0;               /* comp 0 */
             *p++ = 0;               /* huffman table 0 */
    -        *p++ = 1;               /* comp 1 */
    -        *p++ = 0x11;            /* huffman table 1 */
    -        *p++ = 2;               /* comp 2 */
    -        *p++ = 0x11;            /* huffman table 1 */
    +        *p++ = 0x01;               /* comp 1 */
    +        *p++ = cqt != NULL ? 0x11 : 0x00;/* huffman table 1 */
    +        if(cqt != NULL) *p++ = 2;/* comp 2 */
    +        *p++ = cqt != NULL ? 0x11 : 0x00;/* huffman table 1 */
             *p++ = 0;               /* first DCT coeff */
             *p++ = 63;              /* last DCT coeff */
             *p++ = 0;               /* sucessive approx. */

I don't understand the code, but it appears that the "should-say" code is
intended to work as the "says" code works when cqt is not NULL.

However, this change is always operative:

    -        *p++ = 0;               /* comp 0 */
    +        *p++ = 1;               /* comp 1 */

And this change is peculiar, in that the first character assigned to p
changes from 12 to a choice between 18 (0x12) and 11 (0xB).  I wonder if
0x12 is intended to be 12?

    -        *p++ = 12;              /* length lsb */
    -        *p++ = 3;               /* 3 components */
    +        *p++ = cqt != NULL ? 0x12 : 0x0b;/* length lsb */
    +        *p++ = cqt != NULL ? 0x03 : 0x01;/* 3 components */

Dale

--047d7b2e11b1c960ed050dd57667
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Magnus has my input,=C2=A0=C2=A0 I will also include it here=
 in case I was supposed to.</p>
<p dir=3D"ltr">Here is my input and explanation for 4095.</p>
<p dir=3D"ltr">The implementation I have is similar to the annex code I cha=
nged and uses the number of components corresponding to those from the jpeg=
 SOS marker.</p>
<p dir=3D"ltr">The functionality was already hardcoded for two tables and t=
he case of 1 table all the data probably belongs to only the luma table but=
 the table class decided that.</p>
<p dir=3D"ltr">The function definition could be changed to give an array of=
 each components but I believe the maximum number of components is 4 anyway=
 and because its a 4 bit value i ignored it.</p>
<p dir=3D"ltr">This goes back to being compatible and why I opted to change=
 the annex the way I did.</p>
<p dir=3D"ltr">Cases of 0 and 1 table are now handled.</p>
<p dir=3D"ltr">Cases of 2 tables were previously handled (although if they =
use different sizes tables without precision the given code will also fail =
although im not sure this is typically seen as a table usually has either 6=
4 or 128 octets and the same number for each other table generated. )</p>
<p dir=3D"ltr">Cases of 3 also now handled. (With th above notion in mind a=
bout all tables being the same length or requiring precision)</p>
<p dir=3D"ltr">Cases of 4 tables should also be handled in my opinion if th=
ey are not ; but you can&#39;t have a value 4 there...</p>
<p dir=3D"ltr">I believe the code used the three tables to determine if the=
re were any more remaining but I may have omitted that code from the erratu=
m.</p>
<p dir=3D"ltr">In short it may be beneficial to change the function definit=
ion to give those components and their lengths; if that decision is made th=
e result will be easier to follow but I also defer there for your opinion.<=
/p>
<p dir=3D"ltr">There is also a problem using the given standard table on pr=
ogressive encoded images.</p>
<p dir=3D"ltr">I have answered another question related to this here which =
may make more sense.</p>
<p dir=3D"ltr"><a href=3D"http://stackoverflow.com/questions/25662584/how-t=
o-convert-a-jpeg-444-ycbcr-to-422-ycbcr/25676532#25676532">http://stackover=
flow.com/questions/25662584/how-to-convert-a-jpeg-444-ycbcr-to-422-ycbcr/25=
676532#25676532</a></p>
<p dir=3D"ltr">My code is which is working with this method is @ <br>
<a href=3D"http://net7mma.codeplex.com/SourceControl/latest#RtspServer/Medi=
aTypes/RFC2435Media.cs">http://net7mma.codeplex.com/SourceControl/latest#Rt=
spServer/MediaTypes/RFC2435Media.cs</a></p>
<p dir=3D"ltr">The project also has a number of jpeg images to test on whic=
h fail in the annex code, two of which are argb and cmyk.</p>
<p dir=3D"ltr">The latter two would require some custom sdp and the header =
or other informat to be given explicitly there and it should be noted that =
I am not arguing for those formats, just the ones allowed by the baseline s=
pecification which includes progressive.</p>
<p dir=3D"ltr">I do however feel that any updates to the document should al=
low for any jpeg, onvif does this differently and it may work looking at ho=
w they do it to ensure compatible implementations are possible.</p>
<p dir=3D"ltr"><a href=3D"http://www.onvif.org/specs/stream/ONVIF-Streaming=
-Spec-v210.pdf">http://www.onvif.org/specs/stream/ONVIF-Streaming-Spec-v210=
.pdf</a></p>
<p dir=3D"ltr">Thanks,<br>
Julius</p>
<div class=3D"gmail_quot&lt;blockquote class=3D" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">Magnus Westerlund &lt;<a href=
=3D"mailto:magnus.westerlund@ericsson.com">magnus.westerlund@ericsson.com</=
a>&gt; writes:<br>
&gt; I would like to have your feedback on this errata.<br>
&gt;<br>
&gt; It appears to me that the code is hard coded for three components. Tha=
t<br>
&gt; should be pretty evident for anyone reading the comments.<br>
&gt;<br>
&gt; So from that perspective Julius is correct that the code was not takin=
g<br>
&gt; single component images into account. However, it is difficult to<br>
&gt; determine the intention here.<br>
<br>
The code change in the erratum is:<br>
<br>
=C2=A0 =C2=A0 --- says=C2=A0 =C2=A0 2015-01-29 21:21:01.578501194 -0500<br>
=C2=A0 =C2=A0 +++ should-say=C2=A0 =C2=A0 =C2=A0 2015-01-29 21:20:32.139678=
733 -0500<br>
=C2=A0 =C2=A0 @@ -1,4 +1,4 @@<br>
=C2=A0 =C2=A0 -Section Appendix B says:<br>
=C2=A0 =C2=A0 +It should say:<br>
<br>
=C2=A0 =C2=A0 =C2=A0int MakeHeaders(u_char *p, int type, int w, int h, u_ch=
ar *lqt,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0u_char *cqt, u_short dri)<br>
=C2=A0 =C2=A0 @@ -12,7 +12,7 @@<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*p++ =3D 0xd8;=C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /* SOI */<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0p =3D MakeQuantHeader(p, lq=
t, 0);<br>
=C2=A0 =C2=A0 -=C2=A0 =C2=A0 =C2=A0 =C2=A0 p =3D MakeQuantHeader(p, cqt, 1)=
;<br>
=C2=A0 =C2=A0 +=C2=A0 =C2=A0 =C2=A0 =C2=A0 if(cqt !=3D NULL) p =3D MakeQuan=
tHeader(p, cqt, 1);<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0if (dri !=3D 0)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0p =3D MakeDRIHeader(p, dri);<br>
=C2=A0 =C2=A0 @@ -27,7 +27,7 @@<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*p++ =3D w &gt;&gt; 8;=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /* width msb */<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*p++ =3D w;=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* wudth lsb */<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*p++ =3D 3;=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* number of components */<br>
=C2=A0 =C2=A0 -=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D 0;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* comp 0 */<br>
=C2=A0 =C2=A0 +=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D 1;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* comp 1 */<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0if (type =3D=3D 0)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0*p++ =3D 0x21;=C2=A0 =C2=A0 /* hsamp =3D 2, vsamp =3D 1 */<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0else<br>
=C2=A0 =C2=A0 @@ -47,6 +47,8 @@<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0sizeof(lum_ac_codelens)=
,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0lum_ac_symbols,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0sizeof(lum_ac_symbols),=
 0, 1);<br>
=C2=A0 =C2=A0 +=C2=A0 =C2=A0 =C2=A0 =C2=A0 if(cqt !=3D NULL)<br>
=C2=A0 =C2=A0 +=C2=A0 =C2=A0 =C2=A0 =C2=A0 {<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0p =3D MakeHuffmanHeader(p, =
chm_dc_codelens,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0sizeof(chm_dc_codelens)=
,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0chm_dc_symbols,<br>
=C2=A0 =C2=A0 @@ -55,6 +57,7 @@<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0sizeof(chm_ac_codelens)=
,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0chm_ac_symbols,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0sizeof(chm_ac_symbols),=
 1, 1);<br>
=C2=A0 =C2=A0 +=C2=A0 =C2=A0 =C2=A0 =C2=A0}<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 @@ -67,14 +70,14 @@<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*p++ =3D 0xff;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*p++ =3D 0xda;=C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /* SOS */<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*p++ =3D 0;=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* length msb */<br>
=C2=A0 =C2=A0 -=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D 12;=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /* length lsb */<br>
=C2=A0 =C2=A0 -=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D 3;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* 3 components */<br>
=C2=A0 =C2=A0 +=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D cqt !=3D NULL ? 0x12 : =
0x0b;/* length lsb */<br>
=C2=A0 =C2=A0 +=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D cqt !=3D NULL ? 0x03 : =
0x01;/* 3 components */<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*p++ =3D 0;=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* comp 0 */<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*p++ =3D 0;=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* huffman table 0 */<br>
=C2=A0 =C2=A0 -=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D 1;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* comp 1 */<br>
=C2=A0 =C2=A0 -=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D 0x11;=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 /* huffman table 1 */<br>
=C2=A0 =C2=A0 -=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D 2;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* comp 2 */<br>
=C2=A0 =C2=A0 -=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D 0x11;=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 /* huffman table 1 */<br>
=C2=A0 =C2=A0 +=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D 0x01;=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* comp 1 */<br>
=C2=A0 =C2=A0 +=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D cqt !=3D NULL ? 0x11 : =
0x00;/* huffman table 1 */<br>
=C2=A0 =C2=A0 +=C2=A0 =C2=A0 =C2=A0 =C2=A0 if(cqt !=3D NULL) *p++ =3D 2;/* =
comp 2 */<br>
=C2=A0 =C2=A0 +=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D cqt !=3D NULL ? 0x11 : =
0x00;/* huffman table 1 */<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*p++ =3D 0;=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* first DCT coeff */<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*p++ =3D 63;=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /* last DCT coeff */<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*p++ =3D 0;=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* sucessive approx. */<br>
<br>
I don&#39;t understand the code, but it appears that the &quot;should-say&q=
uot; code is<br>
intended to work as the &quot;says&quot; code works when cqt is not NULL.<b=
r>
<br>
However, this change is always operative:<br>
<br>
=C2=A0 =C2=A0 -=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D 0;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* comp 0 */<br>
=C2=A0 =C2=A0 +=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D 1;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* comp 1 */<br>
<br>
And this change is peculiar, in that the first character assigned to p<br>
changes from 12 to a choice between 18 (0x12) and 11 (0xB).=C2=A0 I wonder =
if<br>
0x12 is intended to be 12?<br>
<br>
=C2=A0 =C2=A0 -=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D 12;=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /* length lsb */<br>
=C2=A0 =C2=A0 -=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D 3;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* 3 components */<br>
=C2=A0 =C2=A0 +=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D cqt !=3D NULL ? 0x12 : =
0x0b;/* length lsb */<br>
=C2=A0 =C2=A0 +=C2=A0 =C2=A0 =C2=A0 =C2=A0 *p++ =3D cqt !=3D NULL ? 0x03 : =
0x01;/* 3 components */<br>
<br>
Dale<br>
</div>

--047d7b2e11b1c960ed050dd57667--


From nobody Thu Jan 29 18:38:55 2015
Return-Path: <worley@alum.mit.edu>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B5A01A88F2 for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 18:38:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o6iSzzYSBcn8 for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 18:38:53 -0800 (PST)
Received: from resqmta-po-01v.sys.comcast.net (resqmta-po-01v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:160]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEAB11A88EA for <avt@ietf.org>; Thu, 29 Jan 2015 18:38:52 -0800 (PST)
Received: from resomta-po-15v.sys.comcast.net ([96.114.154.239]) by resqmta-po-01v.sys.comcast.net with comcast id m2eX1p0025AAYLo012esGk; Fri, 30 Jan 2015 02:38:52 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-po-15v.sys.comcast.net with comcast id m2er1p00D1KKtkw012eryh; Fri, 30 Jan 2015 02:38:52 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id t0U2co4Z023526; Thu, 29 Jan 2015 21:38:50 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id t0U2co6j023522; Thu, 29 Jan 2015 21:38:50 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
In-Reply-To: <54C8FED8.1000403@ericsson.com> (magnus.westerlund@ericsson.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Thu, 29 Jan 2015 21:38:50 -0500
Message-ID: <87pp9xgfgl.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1422585532; bh=sJPecFXcSi1z7JjDzw9f8yaUVsK5vrFpBRVoibh63p8=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=GNJTK3OVTpqWL+/Uzl71wiWS88QfGgAbFUs26bUQ8CEmoI++fei8X9479YVUSIOgv m2W0hxXVxF852nkSndWLlU2k3tvReBgMB3blrLJuWFol1ZNrzJ2t03jHKGAXBWLr0R STKkq1PhOIgVdOud+r4TN927BuHLoxxdDv9r0x9Eei1RiJL6YIUmWv51eL+rK2Sufm 02wfmPU7cCQrwleSpde91nC2bL05kcyGyUpZQ3nC1F9DigYGEJUHjHSSlr6YZI8lr2 Zp3hKnPfwISUtD87IIqnaifgoscX0Wje+cL+0RB4QJaqCE6cVVqwnxdHukJ3ChoNCo vi88p0Crasodw==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/jlW6D1GgNWPkiq6lOsdW3adjsWI>
Cc: avt@ietf.org
Subject: Re: [AVTCORE] Errata on RFC 5764 (Errata 3913)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 02:38:54 -0000

Magnus Westerlund <magnus.westerlund@ericsson.com> writes:
> I think a reasonable handling of this one would
> be to put it into the "Held for Documents Update" category.

This makes sense to me, but I think the following sentence is not as
informative as it needs to be:  "STUN messages with methods identifiers
of 1280 or higher cannot be demultiplexed."  The statement should tell
what happens, e.g., "STUN messages with method identifiers of 1280 or
higher are indistinguishable from ***, so such method identifiers must
be avoided when ***."

Dale


From nobody Thu Jan 29 19:10:10 2015
Return-Path: <worley@alum.mit.edu>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 754C21A88E9 for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 19:10:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OO2fQDvTQTJZ for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 19:10:03 -0800 (PST)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D16A1A0270 for <avt@ietf.org>; Thu, 29 Jan 2015 19:10:02 -0800 (PST)
Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111]) by resqmta-ch2-08v.sys.comcast.net with comcast id m39w1p0022Qkjl9013A2na; Fri, 30 Jan 2015 03:10:02 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-ch2-15v.sys.comcast.net with comcast id m3A11p00G1KKtkw013A2e7; Fri, 30 Jan 2015 03:10:02 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id t0U3A1hP027335; Thu, 29 Jan 2015 22:10:01 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id t0U3A0I4027332; Thu, 29 Jan 2015 22:10:00 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Julius Friedman <juliusfriedman@gmail.com>
In-Reply-To: <CACFvNHXyCbQgx3jtzShSQGT9H-TD_Wz7bEkyOB2zfQNjof1VZw@mail.gmail.com> (juliusfriedman@gmail.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Thu, 29 Jan 2015 22:10:00 -0500
Message-ID: <87d25xge0n.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1422587402; bh=BHun/bpmuZ7hQFUST/B6JWsggi5pu9HYK+y0lurxmIY=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=GyjMfPYZQaxwa5C97e6E2ILSmtz/Ph5EhDmccH8LpTVeiGbBZ7SJt5hBjB5j9oxMg ZVQ8Mhq16QpQHD6qbx4Ja/Urnuwaea2zvZeOVI84GBXGWZFMQx30SEyb9v3L+ZoSgH xA3jfqsVnef6RGm4IYOuuUBnuFvAA8j8PH7wJa7Dp8RjWYdNGoA31dbITEfxQZ4RKg g1RQfCP7Eg6sBOY/YZN/zyEmLTZMpnN9R8M9yXD19QCceubHqZoBUMnNOvJQ6yT42A tWUDDl/4bIMTasoB0NewTNugal6hXqs8uMCftf43InW/caSS7g3vFlkpAgZu6N5W8u GEvsEJNNmUrbw==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/j3AOC6_4o9p5QvDI0-e8hlaS8Dc>
Cc: mmusic@ietf.org, avt@ietf.org
Subject: Re: [AVTCORE] New Possible Errata in RFC2326 (And Draft) regarding Blocksize
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 03:10:04 -0000

Julius Friedman <juliusfriedman@gmail.com> writes:
> ", it seems
> to me that it counts only the bytes after the "RTP Fixed Header Fields"
> and any RTP header extensions, and that number legitimately could be
> small (depending on the media encoding in the RTP).
> "
>
> - There must be 12 octets which are the fixed header, this is where that
> information comes from.

That's incorrect.  See the text you quoted earlier:

   12.7 Blocksize

   This request header field is sent from the client to the media server
   asking the server for a particular media packet size. This packet
   size does not include lower-layer headers such as IP, UDP, or
   RTP. [...]

Note that it says "This packet size does not include ... headers such as
... RTP."  The RTP header is *not* counted in this blocksize, so its 12
octets do not constitute a minimum allowed value of blocksize

Dale


From nobody Thu Jan 29 19:43:21 2015
Return-Path: <worley@alum.mit.edu>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A779B1A891C for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 19:43:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.972
X-Spam-Level: 
X-Spam-Status: No, score=0.972 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.972] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CihcGK2X9QRO for <avt@ietfa.amsl.com>; Thu, 29 Jan 2015 19:43:18 -0800 (PST)
Received: from resqmta-po-08v.sys.comcast.net (resqmta-po-08v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:167]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 270EE1A8919 for <avt@ietf.org>; Thu, 29 Jan 2015 19:43:17 -0800 (PST)
Received: from resomta-po-20v.sys.comcast.net ([96.114.154.244]) by resqmta-po-08v.sys.comcast.net with comcast id m3jG1p0075Geu28013jGK7; Fri, 30 Jan 2015 03:43:16 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-po-20v.sys.comcast.net with comcast id m3jF1p00C1KKtkw013jGuH; Fri, 30 Jan 2015 03:43:16 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id t0U3hF4r031104; Thu, 29 Jan 2015 22:43:15 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id t0U3hEGV031101; Thu, 29 Jan 2015 22:43:14 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Julius Friedman <juliusfriedman@gmail.com>
In-Reply-To: <CACFvNHWKMVHceL5PrKozLDWE9-ppXybiP0B7b2C_Lfh9yBBaKQ@mail.gmail.com> (juliusfriedman@gmail.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Thu, 29 Jan 2015 22:43:14 -0500
Message-ID: <871tmdgch9.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1422589396; bh=JF4GXO/11TCccXBMRoOon1r4FP+YDKGGIHcLNbshi4E=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=hZGr6XXAnaDAuyfMQwoBnL7cqrJdsd4kbs5kFneKxTSA1EQvq11k9BbI0xP1PXkt1 JddtQoaaud6A/PhFUPATVIV1ry9XsEn9xQzRbJT70DZlSJMBMcImRYZvBEzu8qwAR0 rgv9e7yHhrqg1GmooaT/8GXmR4gLVNk9mm+L6HGaslkX+HQ6prRYTRNWos4VSUuwr+ T+Isx2WAX3XLma6jg1Hh/qI/itwmhMEbvVULnouUcZTt1EJzffEp/UlUrZ2/F8Yd6l N61rRopUYcf0oyUfn0t3rEIpADSj4/vKtKxZSiM5XUzA098zEHq7O4ALzxelZHMBHt YcXNGqKvwEXTw==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/NypuHRujr5S3b14di9k8GN_WZ34>
Cc: avt@ietf.org, mmusic@ietf.org
Subject: Re: [AVTCORE] [MMUSIC] Question - Erratum 4097
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 03:43:19 -0000

Julius Friedman <juliusfriedman@gmail.com> writes:
> What about another divisor and or some text which states that if there is a
> modulo that the frame height may have to be computed alternately?

I don't understand you here.  You seem to be proposing that another
divisor for representing JPEG size be used, 256 rather than 8.  But that
is an incompatible technical change.  In RFC 2435 there is not intended
to be any alternative way to represent the frame height and width.

> The fact that the image is incorrect makes this errata, the fact that the
> verbiage in the RFC also allows for  via (RFC2435)
>
> 4.1 <https://tools.ietf.org/html/rfc2435#section-4.1>.  The Type Field
>
> Which makes this erratum because images which are advertised as supported
> cannot be viewed or are distorted when the "reference" code is to be used
> with such images and is NOT stated in the RFC....
>
> Please advise.

As far as I can see, you mean to say that the RFC claims to be able to
be able to transmit JPEGs that it cannot.  Can you explain this in more
detail?  (My understanding is that the RFC provides an encoding method
for *some* JPEGs, that the image data is a stream of JPEGs, but not all
JPEGs can be used in RFC 2435 data streams.)

Dale


From nobody Thu Jan 29 21:50:35 2015
Return-Path: <ron.frederick@bluecoat.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD9941A1B79; Thu, 29 Jan 2015 21:11:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.011
X-Spam-Level: 
X-Spam-Status: No, score=-5.011 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j-NS1ZHCn-gP; Thu, 29 Jan 2015 21:11:37 -0800 (PST)
Received: from plsvl-mailgw-01.bluecoat.com (spf.bluecoat.com [199.91.133.11]) by ietfa.amsl.com (Postfix) with ESMTP id E697D1A00F1; Thu, 29 Jan 2015 21:11:36 -0800 (PST)
Received: from PWSVL-EXCHTS-01.internal.cacheflow.com (unknown [10.2.2.122]) by plsvl-mailgw-01.bluecoat.com (Postfix) with ESMTP id 6FEB881A85B; Thu, 29 Jan 2015 21:11:36 -0800 (PST)
Received: from pwsvl-excmbx-05.internal.cacheflow.com ([fe80::f848:d461:9aa9:59a8]) by PWSVL-EXCHTS-01.internal.cacheflow.com ([fe80::5c50:e2ba:8115:4223%19]) with mapi id 14.03.0123.003; Thu, 29 Jan 2015 21:11:36 -0800
From: "Frederick, Ron" <ron.frederick@bluecoat.com>
To: "Dale R. Worley" <worley@ariadne.com>
Thread-Topic: [AVTCORE] [MMUSIC] Question - Erratum 4097
Thread-Index: AQHQPD7ngqiuZTiXpkOv6R37FVCa+ZzYpAuA
Date: Fri, 30 Jan 2015 05:11:34 +0000
Message-ID: <FF2A2B74-4A51-477F-ACA6-82FB9E3C615B@bluecoat.com>
References: <871tmdgch9.fsf@hobgoblin.ariadne.com>
In-Reply-To: <871tmdgch9.fsf@hobgoblin.ariadne.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [199.91.133.71]
Content-Type: text/plain; charset="utf-8"
Content-ID: <A493B92D069B694A9FFCEC5BA63F2E20@bluecoat.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/H0z8AbI6JBds7NMhp78ATRLmyBI>
X-Mailman-Approved-At: Thu, 29 Jan 2015 21:50:30 -0800
Cc: Julius Friedman <juliusfriedman@gmail.com>, "avt@ietf.org" <avt@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [AVTCORE] [MMUSIC] Question - Erratum 4097
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 05:11:42 -0000

T24gSmFuIDI5LCAyMDE1LCBhdCA3OjQzIFBNLCBEYWxlIFIuIFdvcmxleSA8d29ybGV5QGFyaWFk
bmUuY29tPiB3cm90ZToNCj4gSnVsaXVzIEZyaWVkbWFuIDxqdWxpdXNmcmllZG1hbkBnbWFpbC5j
b20+IHdyaXRlczoNCj4+IFdoYXQgYWJvdXQgYW5vdGhlciBkaXZpc29yIGFuZCBvciBzb21lIHRl
eHQgd2hpY2ggc3RhdGVzIHRoYXQgaWYgdGhlcmUgaXMgYQ0KPj4gbW9kdWxvIHRoYXQgdGhlIGZy
YW1lIGhlaWdodCBtYXkgaGF2ZSB0byBiZSBjb21wdXRlZCBhbHRlcm5hdGVseT8NCj4gDQo+IEkg
ZG9uJ3QgdW5kZXJzdGFuZCB5b3UgaGVyZS4gIFlvdSBzZWVtIHRvIGJlIHByb3Bvc2luZyB0aGF0
IGFub3RoZXINCj4gZGl2aXNvciBmb3IgcmVwcmVzZW50aW5nIEpQRUcgc2l6ZSBiZSB1c2VkLCAy
NTYgcmF0aGVyIHRoYW4gOC4gIEJ1dCB0aGF0DQo+IGlzIGFuIGluY29tcGF0aWJsZSB0ZWNobmlj
YWwgY2hhbmdlLiAgSW4gUkZDIDI0MzUgdGhlcmUgaXMgbm90IGludGVuZGVkDQo+IHRvIGJlIGFu
eSBhbHRlcm5hdGl2ZSB3YXkgdG8gcmVwcmVzZW50IHRoZSBmcmFtZSBoZWlnaHQgYW5kIHdpZHRo
Lg0KDQpJIGFncmVlIHdpdGggdGhpcy4gSSBkb27igJl0IHNlZSBhbnkgd2F5IGluIHdoaWNoIHRo
ZSBkaXZpc29yIGNvdWxkIGJlIGNoYW5nZWQgaW4gYSBiYWNrd2FyZCBjb21wYXRpYmxlIG1hbm5l
ci4gQSBkaWZmZXJlbnQgZW5jb2Rpbmcgd291bGQgbmVlZCB0byBiZSBwcm9wb3NlZCB0byBkbyB0
aGlzLCBhbmQgdGhhdCBjYW4ndCBiZSBkb25lIGFzIGFuIGVycmF0YSBvZiBSRkMgMjQzNS4NCg0K
Pj4gVGhlIGZhY3QgdGhhdCB0aGUgaW1hZ2UgaXMgaW5jb3JyZWN0IG1ha2VzIHRoaXMgZXJyYXRh
LCB0aGUgZmFjdCB0aGF0IHRoZQ0KPj4gdmVyYmlhZ2UgaW4gdGhlIFJGQyBhbHNvIGFsbG93cyBm
b3IgIHZpYSAoUkZDMjQzNSkNCj4+IA0KPj4gNC4xIDxodHRwczovL3Rvb2xzLmlldGYub3JnL2h0
bWwvcmZjMjQzNSNzZWN0aW9uLTQuMT4uICBUaGUgVHlwZSBGaWVsZA0KPj4gDQo+PiBXaGljaCBt
YWtlcyB0aGlzIGVycmF0dW0gYmVjYXVzZSBpbWFnZXMgd2hpY2ggYXJlIGFkdmVydGlzZWQgYXMg
c3VwcG9ydGVkDQo+PiBjYW5ub3QgYmUgdmlld2VkIG9yIGFyZSBkaXN0b3J0ZWQgd2hlbiB0aGUg
InJlZmVyZW5jZSIgY29kZSBpcyB0byBiZSB1c2VkDQo+PiB3aXRoIHN1Y2ggaW1hZ2VzIGFuZCBp
cyBOT1Qgc3RhdGVkIGluIHRoZSBSRkMuLi4uDQo+PiANCj4+IFBsZWFzZSBhZHZpc2UuDQo+IA0K
PiBBcyBmYXIgYXMgSSBjYW4gc2VlLCB5b3UgbWVhbiB0byBzYXkgdGhhdCB0aGUgUkZDIGNsYWlt
cyB0byBiZSBhYmxlIHRvDQo+IGJlIGFibGUgdG8gdHJhbnNtaXQgSlBFR3MgdGhhdCBpdCBjYW5u
b3QuICBDYW4geW91IGV4cGxhaW4gdGhpcyBpbiBtb3JlDQo+IGRldGFpbD8gIChNeSB1bmRlcnN0
YW5kaW5nIGlzIHRoYXQgdGhlIFJGQyBwcm92aWRlcyBhbiBlbmNvZGluZyBtZXRob2QNCj4gZm9y
ICpzb21lKiBKUEVHcywgdGhhdCB0aGUgaW1hZ2UgZGF0YSBpcyBhIHN0cmVhbSBvZiBKUEVHcywg
YnV0IG5vdCBhbGwNCj4gSlBFR3MgY2FuIGJlIHVzZWQgaW4gUkZDIDI0MzUgZGF0YSBzdHJlYW1z
LikNCg0KTW9yZXMgc3BlY2lmaWNhbGx5LCB0aGUgUkZDIG9ubHkgZGVmaW5lcyB0eXBlIHZhbHVl
cyB3aGljaCBhbGxvdyB5b3UgdG8gZW5jb2RlIFlVViA0OjI6MiBhbmQgNDoyOjAgSlBFRyBpbWFn
ZXMuIEl0IGFsbG93cyBmb3IgdGhlIHBvc3NpYmlsaXR5IG9mIGVuY29kaW5nIGltYWdlcyBpbiBv
dGhlciBjb2xvciBzcGFjZXMgb3Igd2l0aCBvdGhlciBzYW1wbGluZyBmYWN0b3JzLCBidXQgdGhp
cyB3b3VsZCBuZWVkIHRvIGJlIGRvbmUgYXMgYW4gZXh0ZW5zaW9uIHRvIFJGQyAyNDM1IHdoaWNo
IGRlZmluZXMgdGhlc2Ugb3RoZXIgaXRlbXMgYXMgbmV3IHByZS1kZWZpbmVkIHR5cGUgdmFsdWVz
LCBvciBieSBoYXZpbmcgYW4gYXBwbGljYXRpb24gdXNlIGEgZHluYW1pY2FsbHkgZGVmaW5lZCB0
eXBlIHZhbHVlIGluIHRoZSByYW5nZSAxMjgtMjU1ICh3aGVyZSBib3RoIHNlbmRlciBhbmQgcmVj
ZWl2ZXIga25vdyBob3cgdG8gaW50ZXJwcmV0IHRoaXMgZHluYW1pYyB2YWx1ZSkuDQotLSANClJv
biBGcmVkZXJpY2sNCnJvbmZAYmx1ZWNvYXQuY29tDQoNCg0KDQo=


From nobody Fri Jan 30 01:50:36 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEE0B1A8A87 for <avt@ietfa.amsl.com>; Fri, 30 Jan 2015 01:50:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K4ocLD-7L3Nr for <avt@ietfa.amsl.com>; Fri, 30 Jan 2015 01:50:32 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF93A1A8A85 for <avt@ietf.org>; Fri, 30 Jan 2015 01:50:31 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-1a-54cb53e5e15e
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id B7.4C.04231.5E35BC45; Fri, 30 Jan 2015 10:50:29 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.89) with Microsoft SMTP Server id 14.3.195.1; Fri, 30 Jan 2015 10:50:29 +0100
Message-ID: <54CB53E4.8060300@ericsson.com>
Date: Fri, 30 Jan 2015 10:50:28 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Dale R. Worley" <worley@ariadne.com>
References: <87pp9xgfgl.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87pp9xgfgl.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUyM+Jvje7T4NMhBifWWlu87FnJbvHyRJkD k8fk/V+ZPZYs+ckUwBTFZZOSmpNZllqkb5fAlXFi5R7GgvsCFTfvb2NrYGzj7WLk5JAQMJFo fTyHEcIWk7hwbz1bFyMXh5DAEUaJ1S0bmSGc5YwSt1f9B6viFdCWWDnzDzOIzSKgKvHm1n82 EJtNwELi5o9GMFtUIFhi8fOnrBD1ghInZz5h6WLk4BAR0JToWJADEmYGWty3C2KMsIC5xOuG vSwgtpCAkcS0ba/B4pwCxhLLPy5jhKg3kDiyaA4rhC0v0bx1NjNEvbZEQ1MH6wRGwVlIts1C 0jILScsCRuZVjKLFqcXFuelGxnqpRZnJxcX5eXp5qSWbGIHBenDLb90djKtfOx5iFOBgVOLh 3fD5VIgQa2JZcWXuIUZpDhYlcV4740MhQgLpiSWp2ampBalF8UWlOanFhxiZODilGhhTH89d 9tVsm2Pt93efwl0Cg07McvvLHfvtJv+TSUUhCxyfi8olCTJt1M/Rvc9+fcbcxfVPfqv/v5Jf uCPcbsr0778ztQ/2Xnuc8mHm6mYTlps5K6bUbNZTN1Fp2nwocEeocTn7vfL61iUZfqtMly+b NeuGHUP3aek4u+zVjy+ntVU9qpX2TFZQYinOSDTUYi4qTgQAMW0kLzcCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/QBAUlMjc9rnJBhYU0UjxbddngOM>
Cc: avt@ietf.org
Subject: Re: [AVTCORE] Errata on RFC 5764 (Errata 3913)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 09:50:34 -0000

On 2015-01-30 03:38, Dale R. Worley wrote:
> Magnus Westerlund <magnus.westerlund@ericsson.com> writes:
>> I think a reasonable handling of this one would
>> be to put it into the "Held for Documents Update" category.
> 
> This makes sense to me, but I think the following sentence is not as
> informative as it needs to be:  "STUN messages with methods identifiers
> of 1280 or higher cannot be demultiplexed."  The statement should tell
> what happens, e.g., "STUN messages with method identifiers of 1280 or
> higher are indistinguishable from ***, so such method identifiers must
> be avoided when ***."
> 

Sounds good, if we prepare a replacement for the note, I believe the AD
can edit the Errata.


OLD NEW Text:

Arriving packets may be of types RTP, DTLS, or STUN [RFC5389].
STUN messages with methods identifiers of 1280 or higher cannot
be demultiplexed.
...
                   |       B < 20  -+--> forward to STUN
...
If the value of this byte is less than 20, then the packet is STUN.


New NEW Text:
Arriving packets may be of types RTP, DTLS, or STUN [RFC5389].
STUN messages with method identifiers of 1280 or higher are
indistinguishable from DTLS so such method identifiers must
be avoided when multiplexing the protocols on the same 5-tuple.
...
                   |       B < 20  -+--> forward to STUN
...
If the value of this byte is less than 20, then the packet is STUN.


END OF CHANGE

I also note that one potential critique to accepting it in the current
form, is the issue Cullen raised if we really should assign all of the
0-19 space to STUN or keep that space more limited.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Fri Jan 30 10:42:54 2015
Return-Path: <juliusfriedman@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 976091A017A; Fri, 30 Jan 2015 10:42:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGjdQJMLrVUs; Fri, 30 Jan 2015 10:42:48 -0800 (PST)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D0131A00B9; Fri, 30 Jan 2015 10:42:48 -0800 (PST)
Received: by mail-pa0-f54.google.com with SMTP id eu11so55437785pac.13; Fri, 30 Jan 2015 10:42:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=tedrS7lKCbaQOt7e1EMgfKJYUo6LzX5OPuhyXFlCMDo=; b=XhPep/AE4mw7NNYuBob/fwVxmDyyeqffqfQ6owW7c+e347x1aA9IaoTFlDwWJHI4ih rx/g0DExE+Yp/Jf2XGsvQN0yDfA+bSnFhCRWy+0yoqVtYtqag6KY2+itwFF5PFq2NDQw L5VsWNuQuEO92iMHjPo8a7UV/Ze8DyUYBBNMqDRzl8+8qm/U4DUdy6+m37wPJ4ofQlu8 ODs0GS6MAuRi75ZduidbtxyeUD4hrgufWS20s8supaW3moex+l+HIePN6tbi8IzYb1kL 8w9qQnfFKOYLAZr00nXEuVrcPuXJlbE2DsWC4tML7L6BprLOQNXCuHSKEhLxly9xIA/O q7vg==
MIME-Version: 1.0
X-Received: by 10.68.211.193 with SMTP id ne1mr10763220pbc.49.1422643367278; Fri, 30 Jan 2015 10:42:47 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Fri, 30 Jan 2015 10:42:47 -0800 (PST)
In-Reply-To: <54CB5FED.1010907@ericsson.com>
References: <54C76A07.1090902@ericsson.com> <878uglgdn3.fsf@hobgoblin.ariadne.com> <CACFvNHWXdtXe0+pB=BBVkGpdH5ZOy=gAnkQOHHFrLn8ZLH8Diw@mail.gmail.com> <54CB5FED.1010907@ericsson.com>
Date: Fri, 30 Jan 2015 13:42:47 -0500
Message-ID: <CACFvNHVYZ7NoARvtodKxYKa7WYU5Rq46J8nfrmoRDkKe-wsbsg@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, mmusic@ietf.org, avt@ietf.org
Content-Type: multipart/alternative; boundary=e89a8fb208e88c7f10050de2f8dd
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/9S8MYmeGG7je0znK-tLcluHSLTc>
Subject: Re: [AVTCORE] [MMUSIC] [Technical Errata Reported] RFC2326 (4199)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 18:42:52 -0000

--e89a8fb208e88c7f10050de2f8dd
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Magnus, Et al,

Then Please, adjust what you / we can control which is the Binary
Interleaved Data.

One simple way would be to at least ensure that the application framing
lengths can be conveyed in a manner consistent with the underlying
transport *AND* with respect to any Blocksize in use on the session.

E.g.

A binary interleaved frame MAY NOT contain a frame size larger then any
Blocksize in use.

A binary interleaved frame MAY NOT contain less than 12 bytes for RTP or
RTCP.

A binary interleaved frame MUST be verified by using the packet header
fields e.g. (sequence number, timestamp, ssrc)

Instead of skipping the data what should happen is that the data propagated
to the lower layer transport in chunks.

Skipping data is causing the problem which is also defined as an
instruction when a packet is received for an unknown context, which should
again be handled by propagating the data to the lower layer.

I put this logic in my RtpClient implementation and it works well, and
never becomes unframed unless the client intentionally sends a large packet
which hides data inside (which should be related to the packet anyway)

https://net7mma.codeplex.com/SourceControl/latest#Rtp/RtpClient.cs

You will see in my unit tests I can receive all of the messages which
overflow most other client implementations cannot due to framing errors.

Using the information given and if needed my code as a reference an
implementation can make much better choices and actually never become
unframed and if they do recovering is always possible.

As a take way from this and final note I suppose that someone has also
looked at using independent TCP on a session which also uses Binary
Interleaved data transport, either for RTSP 2 or 1 if not I will ask anyway=
.

The reason for this question is I am revising some parts of my server and
client to be more dependent on a 'session' and that session is typically
tied to a underlying 'Transport'..

My question is

"What happens when a client signals in a single session that it wants to
use TCP Interleaved on one media item and Independent on another"

The result for my implementation is that if the end points overlap then the
framing will contain two additional bytes...

How is this being handled or how SHOULD it be so I can adjust my
implementation to allow for it as such.

I can see how it would work if the end points didn't overlap, the protocol
wouldn't have the RTSP Binary Interleaved header for the media flows using
the independent transport, correct?

But if and when they DO how is that handled?

Should it not be allowed that Binary Interleaved Transfer and Independent
transfer occur in the same session?

If that is the case then what about Binary (TCP/RTP/AVP) and (UDP/)RTP/AVP,
can they occur in the same session? If not why and where does one make that
determination given the information in the RFC either 2326 or BIZ).

I allow for this in my implementation as well and there is no issue (but
caused me to notice that the Session is still active when TEARDOWN occurs
and hence why I filled the other erratum).

Thanks!


On Fri, Jan 30, 2015 at 5:41 AM, Magnus Westerlund <
magnus.westerlund@ericsson.com> wrote:

> Hi,
>
> I would still prefer that this discussion was done on the mailing list.
>
> The content of the Errata is formal broken. But, lets us not care about
> that.
>
> As I have written before, I still don't see how we can make the change
> Julius proposes even to RTSP 2.0. The core of the proposal to address
> this would make so that $ can only occur as starting point of an
> interleaved binary datagram. That appears impossible to me as the URI
> format for example do allow $ to occur in various parts. Putting in
> escaping at all these places at this stage will also be problematic.
>
> Yes, it is sub-optimal it will force clients or server to close the RTSP
> message transport if they become out of synch with message boundaries.
>
> So, in conclusion, I don't see how we can make any corrections or
> improvements on this.
>
> Cheers
>
> Magnus
>
>
> On 2015-01-30 04:30, Julius Friedman wrote:
> > I wrote in about that in a later email.
> >
> > Do you need my comments on that again?
> >
> > This issue is real and does need to be addressed,  either by using
> > hexadecimal notation in all header fields or otherwise by checking the
> > data using the timestamp and sequence numbers of the packets.
> >
> > Invalid packets (length or otherwise) and packets with no context are
> > also issues I ha e brought up.
> >
> > This is much worse when independent TCP is used if used with interleave=
d
> > transport in 1.0 as allowed because even though $ was the worst choice
> > based for a framing value it allows something better then what is
> > required when NO framing at all is used and every read has to be
> > verified to be in sync using the protocol level fields such as timestam=
p
> > and sequence numbers.
> >
> > I have already addressed this in my software as well if reference is
> > needed.
> >
> > Thanks,
> > Julius
> >
> > On Jan 29, 2015 10:18 PM, "Dale R. Worley" <worley@ariadne.com
> > <mailto:worley@ariadne.com>> wrote:
> >
> >     Taking a first look at the erratum, two things occur to me:
> >
> >     The erratum quotes a large chunk of the text of section 4 in both t=
he
> >     "says" and "should say" sections.  IMO the duplicated text should
> have
> >     not been put in either, and instead just the changed part, the
> insertion
> >     of:
> >
> >         *Please note the hexadecimal octet 0x36 should not be included
> >     in any
> >         part of a RTSP message, if present it should be replaced with
> binary
> >         escaped sequence as defined in: <consensus>*.
> >
> >     should have been mentioned in "should say".
> >
> >     The second item is that the proposed addition clearly is not what w=
as
> >     intended.  The text says "the hexadecimal octet 0x36", which is the
> >     ASCII code for the digit "6".  What was intended was "the octet 36"=
,
> >     which is the ASCII code for the character '$'.
> >
> >     Dale
> >
>
>
> --
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> F=C3=A4r=C3=B6gatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
>

--e89a8fb208e88c7f10050de2f8dd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Magnus, Et al,</div><div><br></div><div>Then Please, =
adjust what you / we can control which is the Binary Interleaved Data.</div=
><div><br></div>One simple way would be to at least ensure that the applica=
tion framing lengths can be conveyed in a manner consistent with the underl=
ying transport *AND* with respect to any Blocksize in use on the session.<d=
iv><br></div><div>E.g.</div><div><br></div><div>A binary interleaved frame =
MAY NOT contain a frame size larger then any Blocksize in use.<br></div><di=
v><br></div><div>A binary interleaved frame MAY NOT contain less than 12 by=
tes for RTP or RTCP.</div><div><br></div><div>A binary interleaved frame MU=
ST be verified by using the packet header fields e.g. (sequence number, tim=
estamp, ssrc)</div><div><br></div><div>Instead of skipping the data what sh=
ould happen is that the data propagated to the lower layer transport in chu=
nks.</div><div><br></div><div>Skipping data is causing the problem which is=
 also defined as an instruction when a packet is received for an unknown co=
ntext, which should again be handled by propagating the data to the lower l=
ayer.</div><div><br></div><div>I put this logic in my RtpClient implementat=
ion and it works well, and never becomes unframed unless the client intenti=
onally sends a large packet which hides data inside (which should be relate=
d to the packet anyway)</div><div><br></div><div><a href=3D"https://net7mma=
.codeplex.com/SourceControl/latest#Rtp/RtpClient.cs">https://net7mma.codepl=
ex.com/SourceControl/latest#Rtp/RtpClient.cs</a><br></div><div><br></div><d=
iv>You will see in my unit tests I can receive all of the messages which ov=
erflow most other client implementations cannot due to framing errors.</div=
><div><br></div><div>Using the information given and if needed my code as a=
 reference an implementation can make much better choices and actually neve=
r become unframed and if they do recovering is always possible.</div><div><=
br></div><div>As a take way from this and final note I suppose that someone=
 has also looked at using independent TCP on a session which also uses Bina=
ry Interleaved data transport, either for RTSP 2 or 1 if not I will ask any=
way.</div><div><br></div><div>The reason for this question is I am revising=
 some parts of my server and client to be more dependent on a &#39;session&=
#39; and that session is typically tied to a underlying &#39;Transport&#39;=
..<br></div><div><br></div><div>My question is=C2=A0</div><div><br></div><d=
iv>&quot;What happens when a client signals in a single session that it wan=
ts to use TCP Interleaved on one media item and Independent on another&quot=
;=C2=A0</div><div><br></div><div>The result for my implementation is that i=
f the end points overlap then the framing will contain two additional bytes=
...</div><div><br></div><div>How is this being handled or how SHOULD it be =
so I can adjust my implementation to allow for it as such.</div><div><br></=
div><div>I can see how it would work if the end points didn&#39;t overlap, =
the protocol wouldn&#39;t have the RTSP Binary Interleaved header for the m=
edia flows using the independent transport, correct?</div><div><br></div><d=
iv>But if and when they DO how is that handled?</div><div><br></div><div>Sh=
ould it not be allowed that Binary Interleaved Transfer and Independent tra=
nsfer occur in the same session? =C2=A0</div><div><br></div><div>If that is=
 the case then what about Binary (TCP/RTP/AVP) and (UDP/)RTP/AVP, can they =
occur in the same session? If not why and where does one make that determin=
ation given the information in the RFC either 2326 or BIZ).</div><div><br><=
/div><div>I allow for this in my implementation as well and there is no iss=
ue (but caused me to notice that the Session is still active when TEARDOWN =
occurs and hence why I filled the other erratum).</div><div><br></div><div>=
Thanks!</div><div><br></div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Fri, Jan 30, 2015 at 5:41 AM, Magnus Westerlund <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:magnus.westerlund@ericsson.com" target=3D"=
_blank">magnus.westerlund@ericsson.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">Hi,<br>
<br>
I would still prefer that this discussion was done on the mailing list.<br>
<br>
The content of the Errata is formal broken. But, lets us not care about<br>
that.<br>
<br>
As I have written before, I still don&#39;t see how we can make the change<=
br>
Julius proposes even to RTSP 2.0. The core of the proposal to address<br>
this would make so that $ can only occur as starting point of an<br>
interleaved binary datagram. That appears impossible to me as the URI<br>
format for example do allow $ to occur in various parts. Putting in<br>
escaping at all these places at this stage will also be problematic.<br>
<br>
Yes, it is sub-optimal it will force clients or server to close the RTSP<br=
>
message transport if they become out of synch with message boundaries.<br>
<br>
So, in conclusion, I don&#39;t see how we can make any corrections or<br>
improvements on this.<br>
<br>
Cheers<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Magnus<br>
</font></span><span class=3D"im HOEnZb"><br>
<br>
On 2015-01-30 04:30, Julius Friedman wrote:<br>
&gt; I wrote in about that in a later email.<br>
&gt;<br>
&gt; Do you need my comments on that again?<br>
&gt;<br>
&gt; This issue is real and does need to be addressed,=C2=A0 either by usin=
g<br>
&gt; hexadecimal notation in all header fields or otherwise by checking the=
<br>
&gt; data using the timestamp and sequence numbers of the packets.<br>
&gt;<br>
&gt; Invalid packets (length or otherwise) and packets with no context are<=
br>
&gt; also issues I ha e brought up.<br>
&gt;<br>
&gt; This is much worse when independent TCP is used if used with interleav=
ed<br>
&gt; transport in 1.0 as allowed because even though $ was the worst choice=
<br>
&gt; based for a framing value it allows something better then what is<br>
&gt; required when NO framing at all is used and every read has to be<br>
&gt; verified to be in sync using the protocol level fields such as timesta=
mp<br>
&gt; and sequence numbers.<br>
&gt;<br>
&gt; I have already addressed this in my software as well if reference is<b=
r>
&gt; needed.<br>
&gt;<br>
&gt; Thanks,<br>
&gt; Julius<br>
&gt;<br>
&gt; On Jan 29, 2015 10:18 PM, &quot;Dale R. Worley&quot; &lt;<a href=3D"ma=
ilto:worley@ariadne.com">worley@ariadne.com</a><br>
</span><span class=3D"im HOEnZb">&gt; &lt;mailto:<a href=3D"mailto:worley@a=
riadne.com">worley@ariadne.com</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Taking a first look at the erratum, two things occu=
r to me:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0The erratum quotes a large chunk of the text of sec=
tion 4 in both the<br>
&gt;=C2=A0 =C2=A0 =C2=A0&quot;says&quot; and &quot;should say&quot; section=
s.=C2=A0 IMO the duplicated text should have<br>
&gt;=C2=A0 =C2=A0 =C2=A0not been put in either, and instead just the change=
d part, the insertion<br>
&gt;=C2=A0 =C2=A0 =C2=A0of:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*Please note the hexadecimal octet 0x=
36 should not be included<br>
&gt;=C2=A0 =C2=A0 =C2=A0in any<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0part of a RTSP message, if present it=
 should be replaced with binary<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0escaped sequence as defined in: &lt;c=
onsensus&gt;*.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0should have been mentioned in &quot;should say&quot=
;.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0The second item is that the proposed addition clear=
ly is not what was<br>
&gt;=C2=A0 =C2=A0 =C2=A0intended.=C2=A0 The text says &quot;the hexadecimal=
 octet 0x36&quot;, which is the<br>
&gt;=C2=A0 =C2=A0 =C2=A0ASCII code for the digit &quot;6&quot;.=C2=A0 What =
was intended was &quot;the octet 36&quot;,<br>
&gt;=C2=A0 =C2=A0 =C2=A0which is the ASCII code for the character &#39;$&#3=
9;.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Dale<br>
&gt;<br>
<br>
<br>
</span><div class=3D"HOEnZb"><div class=3D"h5">--<br>
<br>
Magnus Westerlund<br>
<br>
----------------------------------------------------------------------<br>
Services, Media and Network features, Ericsson Research EAB/TXM<br>
----------------------------------------------------------------------<br>
Ericsson AB=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =
Phone=C2=A0 <a href=3D"tel:%2B46%2010%207148287" value=3D"+46107148287">+46=
 10 7148287</a><br>
F=C3=A4r=C3=B6gatan 6=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0| Mobile <a href=3D"tel:%2B46%2073%200949079" value=3D"+467309490=
79">+46 73 0949079</a><br>
SE-164 80 Stockholm, Sweden | mailto: <a href=3D"mailto:magnus.westerlund@e=
ricsson.com">magnus.westerlund@ericsson.com</a><br>
----------------------------------------------------------------------<br>
<br>
</div></div></blockquote></div><br></div>

--e89a8fb208e88c7f10050de2f8dd--

