Multi-party Chat version 08 submitted

“There are some circumstances =
where an endpoint may choose to send an empty SEND =
request”.
I know that bodiless SEND =
requests are different from SEND requests with empty bodies. But what =
could be the use case for the same??
I know that bodiless SEND requests are different =
from SEND requests with empty bodies. But what could be the use case for =
the same??
“Previous versions of this =
document included a mechanism to =
negotiate
   the direction for =
any required TCP connection.  The mechanism =
was
   loosely based on the =
Connection-Oriented Media (COMEDIA) [26] =
work
   done by the MMUSIC =
working group.  The primary motivation was =
to
   allow MSRP sessions =
to succeed in situations where the offerer =
could
   not accept =
connections but the answerer could.  For example, =
the
   offerer might be =
behind a NAT, while the answerer might have =
a
   globally routable =
address.
    The SIMPLE working =
group chose to remove that mechanism from MSRP, =
as
   it added a great =
deal of complexity to connection =
management.
   Instead, MSRP now =
specifies a default connection direction.  =
The
   party that sent the =
original offer is responsible for connecting =
to
   its =
peer.”

Does
this mean that in order to resolve NAT traversal issue in MSRP, using =
MSRP relays
is the only solution??

In
other words does this indicates that if MSRP relays are not used then =
COMEDIA
has to be used (which as per rfc 4975 is deprecated)?? =

Regards

Achint
Aggarwal

   the direction for any required TCP =
connection.  The mechanism was
   loosely based on the =
Connection-Oriented Media (COMEDIA) [26] =
work
   allow MSRP sessions to succeed in =
situations where the offerer could
   not accept connections but the =
answerer could.  For example, =
the
   it added a great deal of complexity to =
connection management.
   Instead, MSRP now specifies a default =
connection direction.  The
   party that sent the original offer is =
responsible for connecting to
   its =
peer.=94
Does this mean that in order to =
resolve NAT traversal issue in MSRP, using MSRP relays is the only =
solution??
=93For client-to-client communication, the sender =
of a message typically
   opens a new TCP connection (with or =
without TLS) if one is needed.
   Relays reuse existing connections =
first, but can open new connections
   (typically to other relays) to =
deliver requests such as SEND or
   =
REPORT.=94
Consider a scenario where an MSRP =
client establishes an MSRP session and client=92s relay opens a =
connection with its next hop to route the MSRP packets coming to it from =
the client.
=93For client-to-client communication, the sender =
of a message typically
   opens a new TCP connection (with or =
without TLS) if one is needed.
   Relays reuse existing connections =
first, but can open new connections
   (typically to other relays) to =
deliver requests such as SEND or
   =
REPORT.=94
Consider a scenario where an MSRP =
client establishes an MSRP session and client=92s relay opens a =
connection with its next hop to route the MSRP packets coming to it from =
the client.
=93For client-to-client communication, the sender =
of a message typically
   opens a new TCP connection (with or =
without TLS) if one is needed.
   Relays reuse existing connections =
first, but can open new connections
   (typically to other relays) to =
deliver requests such as SEND or
   =
REPORT.=94
Consider a scenario where an MSRP =
client establishes an MSRP session and client=92s relay opens a =
connection with its next hop to route the MSRP packets coming to it from =
the client.
=93For client-to-client communication, the sender =
of a message typically
   opens a new TCP connection (with or =
without TLS) if one is needed.
   Relays reuse existing connections =
first, but can open new connections
   (typically to other relays) to =
deliver requests such as SEND or
   =
REPORT.=94
Consider a scenario where an MSRP =
client establishes an MSRP session and client=92s relay opens a =
connection with its next hop to route the MSRP packets coming to it from =
the client.