draft-ietf-mmusic-media-loopback-06.txt   draft-ietf-mmusic-media-loopback-07.txt 
K. Hedayat K. Hedayat
Internet Draft Brix Networks Internet Draft Brix Networks
Expires: October 2007 P. Jones Expires: June 2008 P. Jones
Cisco Systems, Inc. Cisco Systems, Inc.
A. Roychowdhury A. Roychowdhury
Hughes Hughes
C. SivaChelvan C. SivaChelvan
Cisco Systems, Inc. Cisco Systems, Inc.
N. Stratton N. Stratton
November 2007
An Extension to the Session Description Protocol (SDP) for Media An Extension to the Session Description Protocol (SDP) for Media
Loopback Loopback
draft-ietf-mmusic-media-loopback-06 draft-ietf-mmusic-media-loopback-07
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 3, line 8 skipping to change at page 3, line 8
9. Congestion Control...........................................15 9. Congestion Control...........................................15
10. Examples....................................................15 10. Examples....................................................15
10.1 Offer for specific media loopback type..................15 10.1 Offer for specific media loopback type..................15
10.2 Offer for choice of media loopback type.................16 10.2 Offer for choice of media loopback type.................16
10.3 Offer for choice of media loopback type with 10.3 Offer for choice of media loopback type with
rtp-start-loopback...........................................17 rtp-start-loopback...........................................17
10.4 Response to INVITE request rejecting loopback media.....18 10.4 Response to INVITE request rejecting loopback media.....18
10.5 Response to INVITE request rejecting loopback media with 10.5 Response to INVITE request rejecting loopback media with
rtp-start-loopback...........................................18 rtp-start-loopback...........................................18
11. Security Considerations.....................................19 11. Security Considerations.....................................19
12. IANA Considerations.........................................20 12. Implementation Considerations...............................20
13. Acknowledgements............................................20 13. IANA Considerations.........................................20
14. References..................................................20 14. Acknowledgements............................................20
15. Normative References........................................20
1. Introduction 1. Introduction
The overall quality, reliability, and performance of VoIP, The overall quality, reliability, and performance of VoIP,
Real-time Text and Video over IP services rely on the performance Real-time Text and Video over IP services rely on the performance
and quality of the media path. In order to assure the quality of and quality of the media path. In order to assure the quality of
the delivered media there is a need to monitor the performance of the delivered media there is a need to monitor the performance of
the media transport. One method of monitoring and managing the the media transport. One method of monitoring and managing the
overall quality of VoIP, Real-time Text and Video over IP Services overall quality of VoIP, Real-time Text and Video over IP Services
is through monitoring the quality of the media in an active is through monitoring the quality of the media in an active
skipping to change at page 20, line 5 skipping to change at page 20, line 5
11. Security Considerations 11. Security Considerations
The security considerations of [RFC3261] apply. Furthermore, given The security considerations of [RFC3261] apply. Furthermore, given
that media loopback may be automated without the end user's that media loopback may be automated without the end user's
knowledge, the server of the media loopback should be aware of knowledge, the server of the media loopback should be aware of
denial of service attacks. It is recommended that sessions with denial of service attacks. It is recommended that sessions with
media loopback are authenticated and the frequency of such sessions media loopback are authenticated and the frequency of such sessions
is limited by the server. is limited by the server.
12. IANA Considerations 12. Implementation Considerations
The media loopback approach described in this document is a
complete solution that would work under all scenarios. However, it
is believed that the solution may not be light-weight enough for
the common case. In light of this concern, this section clarifies
which features of the loopback proposal MUST be implemented for all
implementations and which features MAY be deferred if the complete
solution is not desired.
All implementations MUST support the rtp-pkt-loopback option for
loopback-type attribute. In addition, for the loopback-mode
attribute, all implementations of an offerer MUST at a minimum be
able to act as a loopback-source. All implementation MUST also at a
minimum support the direct media loopback payload type. Remaining
attribute values including rtp-media-loopback and
rtp-start-loopback MAY be implemented in complete implementations
of this draft.
13. IANA Considerations
There are no IANA considerations associated with this There are no IANA considerations associated with this
specification. specification.
13. Acknowledgements 14. Acknowledgements
The authors wish to thank Nagarjuna Venna, Flemming Andreasen, Jeff The authors wish to thank Nagarjuna Venna, Flemming Andreasen, Jeff
Bernstein, Paul Kyzivat, and Dave Oran for their comments and Bernstein, Paul Kyzivat, and Dave Oran for their comments and
suggestions. suggestions.
14. References 15. Normative References
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G.,
Johnston, A., Peterson, J., Sparks, R., Handley, M. Johnston, A., Peterson, J., Sparks, R., Handley, M.
and E. Schooler, "SIP: Session Initiation Protocol", and E. Schooler, "SIP: Session Initiation Protocol",
RFC 3261, June 2002. RFC 3261, June 2002.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer
Model with the Session Description Protocol (SDP)", Model with the Session Description Protocol (SDP)",
RFC 3264, June 2002. RFC 3264, June 2002.
skipping to change at page 22, line 23 skipping to change at page 22, line 39
Nathan Stratton Nathan Stratton
663 Salem St. 663 Salem St.
Lynnfield, MA 01940 Lynnfield, MA 01940
Phone: +1 410 908 7587 Phone: +1 410 908 7587
EMail: nathan@robotics.net EMail: nathan@robotics.net
URI: http://www.robotics.net/ URI: http://www.robotics.net/
IPR Disclosure Acknowledgement Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed Intellectual Property Rights or other rights that might be claimed
to pertain to the implementation or use of the technology described to pertain to the implementation or use of the technology described
in this document or the extent to which any license under such in this document or the extent to which any license under such
rights might or might not be available; nor does it represent that rights might or might not be available; nor does it represent that
it has made any independent effort to identify any such rights. it has made any independent effort to identify any such rights.
Information on the procedures with respect to rights in RFC Information on the procedures with respect to rights in RFC
documents can be found in BCP 78 and BCP 79. documents can be found in BCP 78 and BCP 79.
skipping to change at page 23, line 5 skipping to change at page 23, line 38
of such proprietary rights by implementers or users of this of such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository specification can be obtained from the IETF on-line IPR repository
at http://www.ietf.org/ipr. at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Copyright Notice Acknowledgement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 10 change blocks. 
27 lines changed or deleted 50 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/