draft-ietf-mmusic-sdp-srcfilter-06.txt   draft-ietf-mmusic-sdp-srcfilter-07.txt 
Network Working Group Bob Quinn Network Working Group Bob Quinn
INTERNET-DRAFT Celox Networks INTERNET-DRAFT Celox Networks
Category: Standards Track Ross Finlayson Category: Standards Track Ross Finlayson
Expires: January 2005 LIVE.COM Expires: December 2005 LIVE.COM
July 18, 2004 June 6, 2005
Session Description Protocol (SDP) Source Filters Session Description Protocol (SDP) Source Filters
<draft-ietf-mmusic-sdp-srcfilter-06.txt> <draft-ietf-mmusic-sdp-srcfilter-07.txt>
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that
patent or other IPR claims of which I am aware have been disclosed, any applicable patent or other IPR claims of which he or she is
or will be disclosed, and any of which I become aware will be aware have been or will be disclosed, and any of which he or she
disclosed, in accordance with RFC 3668. becomes 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 other Task Force (IETF), its areas, and its working groups. Note that
groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or cite them other than as "work in progress". material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Abstract Abstract
This document describes how to adapt the Session Description Protocol This document describes how to adapt the Session Description Protocol
(SDP) to express one or more source addresses as a source filter for (SDP) to express one or more source addresses as a source filter for
one or more destination "connection" addresses. It defines the one or more destination "connection" addresses. It defines the
syntax and semantics for an SDP "source-filter" attribute that may syntax and semantics for an SDP "source-filter" attribute that may
skipping to change at line 239 skipping to change at line 241
<media-description 2> = <media-description 2> =
m=video 54322 RTP/AVP 34 m=video 54322 RTP/AVP 34
3.2.1. Source-Specific Multicast Example 3.2.1. Source-Specific Multicast Example
Multicast addresses in the Source-Specific Multicast [SSM] range Multicast addresses in the Source-Specific Multicast [SSM] range
require a single unicast sender address for each multicast require a single unicast sender address for each multicast
destination, so the source-filter specification provides a natural destination, so the source-filter specification provides a natural
fit. In this example, a session member should receive only traffic fit. In this example, a session member should receive only traffic
sent from 192.168.9.10 to the multicast session address 232.3.4.5. sent from 192.0.2.10 to the multicast session address 232.3.4.5.
<session-description> <session-description>
c=IN IP4 232.3.4.5/127 c=IN IP4 232.3.4.5/127
a=source-filter: incl IN IP4 232.3.4.5 192.168.9.10 a=source-filter: incl IN IP4 232.3.4.5 192.0.2.10
<media-description 1> <media-description 1>
This source filter example uses an inclusion list with a single This source filter example uses an inclusion list with a single
multicast "connection-address" as the destination and single unicast multicast "connection-address" as the destination and single unicast
address as the source. Note that the value of the connection-address address as the source. Note that the value of the connection-address
matches the value specified in the connection-field. matches the value specified in the connection-field.
Also note that since the connection-field is located in the session- Also note that since the connection-field is located in the session-
description section, the source-filter applies to all media. description section, the source-filter applies to all media.
skipping to change at line 276 skipping to change at line 278
a=rtcp: unicast ... a=rtcp: unicast ...
attribute, as described in [RTCP-SSM] (section 10.1). This specifies attribute, as described in [RTCP-SSM] (section 10.1). This specifies
that RTCP "Reception Report" (RR) packets are to be sent back via that RTCP "Reception Report" (RR) packets are to be sent back via
unicast. unicast.
3.2.2. Unicast Exclusion Example 3.2.2. Unicast Exclusion Example
Typically, an SDP session <connection-address> value is a multicast Typically, an SDP session <connection-address> value is a multicast
address, although it is also possible to use either a unicast address, although it is also possible to use either a unicast
address or FQDN. This example illustrates a scenario whereby a address or FQDN. This example illustrates a scenario whereby a
session description indicates the unicast source address 192.168.9.10 session description indicates the unicast source address 192.0.2.10
in an exclusion filter. In effect, this sample source-filter says, in an exclusion filter. In effect, this sample source-filter says,
"destination 192.168.10.11 should accept traffic from any sender "destination 192.0.2.11 should accept traffic from any sender
*except* 192.168.9.10." *except* 192.0.2.10."
<session-description> <session-description>
c=IN IP4 192.168.10.11 c=IN IP4 192.0.2.11
a=source-filter: excl IN IP4 192.168.10.11 192.168.9.10 a=source-filter: excl IN IP4 192.0.2.11 192.0.2.10
<media-description 1> <media-description 1>
3.2.3. Multiple Session Address Example 3.2.3. Multiple Session Address Example
This source-filter example uses the wildcard "*" value for This source-filter example uses the wildcard "*" value for
<dest-addr> to correspond to any/all <connection-address> values. <dest-addr> to correspond to any/all <connection-address> values.
Hence, the only legitimate source for traffic sent to either Hence, the only legitimate source for traffic sent to either
232.2.2.2 or 232.4.4.4 multicast addresses is 192.168.9.10. 232.2.2.2 or 232.4.4.4 multicast addresses is 192.0.2.10.
Traffic sent from any other unicast source address should be Traffic sent from any other unicast source address should be
discarded by the receiver. discarded by the receiver.
<session-description> <session-description>
a=source-filter: incl IN IP4 * 192.168.9.10 a=source-filter: incl IN IP4 * 192.0.2.10
<media-description 1> <media-description 1>
c=IN IP4 232.2.2.2/127 c=IN IP4 232.2.2.2/127
<media-description 2> <media-description 2>
c=IN IP4 232.4.4.4/63 c=IN IP4 232.4.4.4/63
3.2.4. Multiple Multicast Address Example 3.2.4. Multiple Multicast Address Example
In this example, the <connection-address> specifies three multicast In this example, the <connection-address> specifies three multicast
addresses: 224.2.1.1, 224.2.1.2, and 224.2.1.3. The first and third addresses: 224.2.1.1, 224.2.1.2, and 224.2.1.3. The first and third
of these addresses are given source filters. However, in this of these addresses are given source filters. However, in this
example the second address - 224.2.1.2 - is *not* given a example the second address - 224.2.1.2 - is *not* given a
source filter. source filter.
<session-description> <session-description>
c=IN IP4 224.2.1.1/127/3 c=IN IP4 224.2.1.1/127/3
a=source-filter: incl IN IP4 224.2.1.1 192.168.9.10 a=source-filter: incl IN IP4 224.2.1.1 192.0.2.10
a=source-filter: incl IN IP4 224.2.1.3 192.168.9.42 a=source-filter: incl IN IP4 224.2.1.3 192.0.2.42
<media-description 1> <media-description 1>
3.2.5. IPv6 Multicast Source-Filter Example 3.2.5. IPv6 Multicast Source-Filter Example
This simple example defines a single session-level source-filter that This simple example defines a single session-level source-filter that
references a single IPv6 multicast destination and source pair. The references a single IPv6 multicast destination and source pair. The
IP multicast traffic sent to FFOE::11A is valid only from the unicast IP multicast traffic sent to FFOE::11A is valid only from the unicast
source address 2001:210:1:2:240:96FF:FE25:8EC9 source address 2001:DB8:1:2:240:96FF:FE25:8EC9
<session-description> <session-description>
c=IN IP6 FF0E::11A/127 c=IN IP6 FF0E::11A/127
a=source-filter incl IN IP6 FF0E::11A 2001:210:1:2:240:96FF:FE25:8EC9 a=source-filter incl IN IP6 FF0E::11A 2001:DB8:1:2:240:96FF:FE25:8EC9
<media-description 1> <media-description 1>
3.2.6. IPv4 and IPv6 FQDN Example 3.2.6. IPv4 and IPv6 FQDN Example
This example illustrates use of the <addrtype> "*" wildcard, along This example illustrates use of the <addrtype> "*" wildcard, along
with multicast and source FQDNs that may resolve to either an IPv6 with multicast and source FQDNs that may resolve to either an IPv6
or IPv4 address, or both. Although typically both the multicast and or IPv4 address, or both. Although typically both the multicast and
source addresses will be the same (either both IPv4 or IPv6), using source addresses will be the same (either both IPv4 or IPv6), using
the wildcard for addrtype in the source filter allows asymmetry the wildcard for addrtype in the source filter allows asymmetry
skipping to change at line 457 skipping to change at line 459
8. Normative References 8. Normative References
[ABNF] Crocker, D., P. Overell, "Augmented BNF for Syntax [ABNF] Crocker, D., P. Overell, "Augmented BNF for Syntax
Specifications: ABNF," RFC 2234, November 1997. Specifications: ABNF," RFC 2234, November 1997.
[REQMNT] Bradner, S., "Key words for use in RFCs to Indicate [REQMNT] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels," BCP 14, RFC 2119, March 1997. Requirement Levels," BCP 14, RFC 2119, March 1997.
[RTCP-SSM] Chesterfield, J., E. Schooler, J. Ott, [RTCP-SSM] Chesterfield, J., E. Schooler, J. Ott,
"RTCP Extensions for Single-Source Multicast Sessions "RTCP Extensions for Single-Source Multicast Sessions
with Unicast Feedback," Work in progress, March 2003. with Unicast Feedback," Work in progress, October 2004
[SDP] Handley, M., V. Jacobson, C. Perkins, [SDP] Handley, M., V. Jacobson, C. Perkins,
"SDP: Session Description Protocol," "SDP: Session Description Protocol,"
Work in Progress, March 2003. Work in Progress, February 2005.
[UTF-8] Yergeau, F., "UTF-8, a transformation format of Unicode [UTF-8] Yergeau, F., "UTF-8, a transformation format of
and ISO 10646," RFC 2044, October 1996. ISO 10646," RFC 3629, October 1996.
9. Informative References 9. Informative References
[CA-96.21] CERT Advisory CA-96.21, "TCP SYN Flooding and IP [CA-96.21] CERT Advisory CA-96.21, "TCP SYN Flooding and IP
Spoofing Attacks," September 1996. Spoofing Attacks," September 1996.
[IGMPv1] Deering, S., "Host Extensions for IP Multicasting," [IGMPv1] Deering, S., "Host Extensions for IP Multicasting,"
RFC 1112 (STD 5), August 1989. RFC 1112 (STD 5), August 1989.
[IGMPv3] Cain, B. et al. "Internet Group Management Protocol, [IGMPv3] Cain, B. et al. "Internet Group Management Protocol,
Version 3,", Work in progress, May 2002. Version 3,", RFC 3376, October 2002.
[MSF API] Thaler, D., B. Fenner, B. Quinn, "Socket Interface [MSF API] Thaler, D., B. Fenner, B. Quinn, "Socket Interface
Extensions for Multicast Source Filters," Extensions for Multicast Source Filters,"
Work in progress, July 2002. RFC 3678, January 2004.
[OFFER] Rosenberg, J., H. Schulzrinne, "An Offer/Answer Model [OFFER] Rosenberg, J., H. Schulzrinne, "An Offer/Answer Model
with the Session Description Protocol (SDP)", with the Session Description Protocol (SDP)",
RFC 3264, June 2002. RFC 3264, June 2002.
[SSM] Bhattacharyya, S. et al., "An Overview of Source-Specific [SSM] Bhattacharyya, S. et al., "An Overview of Source-Specific
Multicast (SSM)," Work in progress, October 2002. Multicast (SSM)," RFC 3569, July 2003.
10. Authors' Addresses 10. Authors' Addresses
Bob Quinn Bob Quinn
Celox Networks Celox Networks
2 Park Central Drive 2 Park Central Drive
Southborough, MA 01772 Southborough, MA 01772
phone: 508-305-7000 phone: 508-305-7000
email: bquinn (at) celoxnetworks.com email: bquinn (at) celoxnetworks.com
skipping to change at line 529 skipping to change at line 531
at http://www.ietf.org/ipr. at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention The IETF invites any interested party to bring to its attention
any copyrights, patents or patent applications, or other any copyrights, patents or patent applications, or other
proprietary rights that may cover technology that may be required proprietary rights that may cover technology that may be required
to implement this standard. Please address the information to the to implement this standard. Please address the information to the
IETF at ietf-ipr@ietf.org. IETF at ietf-ipr@ietf.org.
12. Copyright Notice 12. Copyright Notice
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005).
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. 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 This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Appendix A. Source-Filter Attribute Syntax Appendix A. Source-Filter Attribute Syntax
skipping to change at line 554 skipping to change at line 558
an exclusion or inclusion list of one or more (IPv4 or IPv6) unicast an exclusion or inclusion list of one or more (IPv4 or IPv6) unicast
source addresses. It is intended as an extension to the grammar for source addresses. It is intended as an extension to the grammar for
the Session Description Protocol, as defined in [SDP]. Specifically, the Session Description Protocol, as defined in [SDP]. Specifically,
it describes the syntax for the new "source-filter" attribute field, it describes the syntax for the new "source-filter" attribute field,
which MAY be either a session-level or media-level attribute. which MAY be either a session-level or media-level attribute.
The "connection-address" value in each source filter field MUST match The "connection-address" value in each source filter field MUST match
an existing connection-field value, unless the wildcard connection- an existing connection-field value, unless the wildcard connection-
address value "*" is specified. address value "*" is specified.
source-filter = "source-filter" ":" filter-mode filter-spec source-filter = "source-filter" ":" SP filter-mode SP filter-spec
; SP is the ASCII 'space' character
; (0x20, defined in [ABNF]).
filter-mode = "excl" / "incl" filter-mode = "excl" / "incl"
; either exclusion or inclusion mode ; either exclusion or inclusion mode
filter-spec = nettype address-types dest-address src-list filter-spec = nettype SP address-types SP dest-address SP src-list
; nettype is as defined in [SDP]. ; nettype is as defined in [SDP].
address-types = "*" / addrtype address-types = "*" / addrtype
; "*" for all address types (both IP4 and IP6), ; "*" for all address types (both IP4 and IP6),
; but only when <dest-address> and <src-list> ; but only when <dest-address> and <src-list>
; reference FQDNs. ; reference FQDNs.
; addrtype is as defined in [SDP]. ; addrtype is as defined in [SDP].
dest-address = "*" / IP4-address / IP6-address / FQDN dest-address = "*" / IP4-address / IP6-address / FQDN
; "*" applies to all connection-address values. ; "*" applies to all connection-address values.
; IP4-address, IP6-address, FQDN are as defined ; IP4-address, IP6-address, FQDN are as defined
; in [SDP]. ; in [SDP].
src-list = *(addr SP) addr src-list = *(addr SP) unicast-address
; one or more unicast source addresses (in ; one or more unicast source addresses (in
; standard IPv4 or IPv6 ASCII-notation form) ; standard IPv4 or IPv6 ASCII-notation form)
; or FQDNs. ; or FQDNs.
; addr is as defined in [SDP]. ; unicast-address is as defined in [SDP].
; SP is the ASCII 'space' character
; (0x20, defined in [ABNF]).
Expires: January 2005 July 18, 2004 Expires: December 2005 June 6, 2005
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/