draft-ietf-fecframe-config-signaling-08.txt   draft-ietf-fecframe-config-signaling-09.txt 
FECFRAME Working Group Rajiv Asati FECFRAME Working Group Rajiv Asati
Internet Draft Cisco Systems Internet Draft Cisco Systems
Intended status: Informational Intended status: Informational
Expires: July 2012 Expires: July 2012
February 25, 2012 June 8, 2012
Methods to convey FEC Framework Configuration Information Methods to convey FEC Framework Configuration Information
draft-ietf-fecframe-config-signaling-08.txt draft-ietf-fecframe-config-signaling-09.txt
Abstract Abstract
FEC Framework document [RFC6363] defines the FEC Framework FEC Framework document [RFC6363] defines the FEC Framework
Configuration Information necessary for the FEC framework operation. Configuration Information necessary for the FEC framework operation.
This document describes how to use signaling protocols such as This document describes how to use signaling protocols such as
Session Announcement Protocol (SAP), Session Initiation Protocol Session Announcement Protocol (SAP), Session Initiation Protocol
(SIP), Real Time Stream Protocol (RTSP) etc. for determining and (SIP), Real Time Stream Protocol (RTSP) etc. for determining and
communicating the Configuration information between sender(s) and communicating the Configuration information between sender(s) and
receiver(s). receiver(s).
skipping to change at page 2, line 13 skipping to change at page 2, line 13
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference 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 August 25, 2012. This Internet-Draft will expire on November 8, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 8, line 15 skipping to change at page 8, line 15
5.1. Signaling Protocol for Multicasting 5.1. Signaling Protocol for Multicasting
This specification describes using Session Announcement Protocol This specification describes using Session Announcement Protocol
(SAP) version 2 [RFC2974] as the signaling protocol to multicast the (SAP) version 2 [RFC2974] as the signaling protocol to multicast the
configuration information from one sender to many receivers. The configuration information from one sender to many receivers. The
apparent advantage is that the server doesn't need to maintain any apparent advantage is that the server doesn't need to maintain any
state for any receiver using SAP. state for any receiver using SAP.
SAP messages are carried over UDP over IP with destination UDP SAP messages are carried over UDP over IP with destination UDP
port being 9875 and source UDP port being any available number, port being 9875 and source UDP port being any available number,
as described in RFC2974. The SAP message(s) should contain an as described in RFC2974. The SAP message(s) MUST contain an
authentication header using PGP authentication. authentication header using PGP authentication.
At the high level, a sender, acting as the SAP announcer, signals At the high level, a sender, acting as the SAP announcer, signals
the FEC Framework Configuration Information for each FEC Framework the FEC Framework Configuration Information for each FEC Framework
instance available at the sender, using the SAP message(s). The instance available at the sender, using the SAP message(s). The
configuration information, encoded in a suitable format as per the configuration information, encoded in a suitable format as per the
section 4.1, is carried in the Payload of the SAP message(s). A section 4.1, is carried in the Payload of the SAP message(s). A
receiver, acting as the SAP listener, listens on a well-known UDP receiver, acting as the SAP listener, listens on a well-known UDP
port and at least one well known multicast group IP address (as port and at least one well known multicast group IP address (as
explained in the section 5.1.1). This enables the receiver to explained in the section 5.1.1). This enables the receiver to
 End of changes. 4 change blocks. 
4 lines changed or deleted 4 lines changed or added

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