draft-ietf-mboned-session-announcement-req-02.txt   draft-ietf-mboned-session-announcement-req-03.txt 
MBONED Working Group H. Asaeda MBONED Working Group H. Asaeda
Internet-Draft Keio University Internet-Draft Keio University
Intended status: Informational V. Roca Intended status: Informational V. Roca
Expires: April 29, 2010 INRIA Expires: September 9, 2010 INRIA
October 26, 2009 March 8, 2010
Requirements for IP Multicast Session Announcement Requirements for IP Multicast Session Announcement
draft-ietf-mboned-session-announcement-req-02 draft-ietf-mboned-session-announcement-req-03
Abstract
The Session Announcement Protocol (SAP) [2] was used to announce
information for all available IP multicast sessions to the
prospective receiver in an experimental network. It is easy to use,
but not scalable and difficult to control the SAP message
transmission in a wide area network. This document describes the
issues and the requirements for multicast session announcement in the
global Internet.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79.
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. 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 to 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/ietf/1id-abstracts.txt.
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.
This Internet-Draft will expire on April 29, 2010. This Internet-Draft will expire on September 9, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.
The Session Announcement Protocol (SAP) [2] was used to announce This document may contain material from IETF Documents or IETF
information for all available IP multicast sessions to the Contributions published or made publicly available before November
prospective receiver in an experimental network. It is easy to use, 10, 2008. The person(s) controlling the copyright in some of this
but not scalable and difficult to control the SAP message material may not have granted the IETF Trust the right to allow
transmission in a wide area network. This document describes the modifications of such material outside the IETF Standards Process.
issues and the requirements for multicast session announcement in the Without obtaining an adequate license from the person(s) controlling
global Internet. the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Potential Problems in SAP . . . . . . . . . . . . . . . . . . 6 3. Potential Problems in SAP . . . . . . . . . . . . . . . . . . 6
3.1. Announcement Interval vs. Latency . . . . . . . . . . . . 6 3.1. Announcement Interval vs. Latency . . . . . . . . . . . . 6
3.2. Difficulties in Scope Definition . . . . . . . . . . . . . 6 3.2. Difficulties in Scope Definition . . . . . . . . . . . . . 6
3.3. ASM Dependency . . . . . . . . . . . . . . . . . . . . . . 7 3.3. ASM Dependency . . . . . . . . . . . . . . . . . . . . . . 7
4. Lack of Sender and Receiver Control in Announcement . . . . . 9 4. Lack of Sender and Receiver Control in Announcement . . . . . 9
 End of changes. 7 change blocks. 
29 lines changed or deleted 35 lines changed or added

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