Re: [Fecframe] Fecframe Digest, Vol 25, Issue 9

Thanks for expanding it, Marshall. 

The cited problem is one of the reasons why section 4.1.1 of the
draft-asati-fecframe-config-signaling-00 includes simpler interval
definition so as to avoid having SAP to calculate the interval in an
adaptive manner.

~~~~~~~~~~~~~
4.1.1. Sender Procedure 

	....

   The sender must periodically send the 'SAP announcement' message. 
   This is required so that the receiver doesn't purge the cached 
   entry(s) from the database and doesn't trigger the deletion of FEC 
   Framework configuration information. While the time interval between 
   repetitions of an announcement can be calculated as per the very 
   sophisticated but complex formula explained in RFC2974, the preferred

   and simpler mean is to let the user specify the time interval from 
   the range of 1-60 mins with suggested default being 10 mins. The 
   implementation of signaling protocol should provide the flexibility 
   to the operator to choose the complex method over the simpler method 
   of determining the SAP announcement time interval. 
 ~~~~~~~~~~~~~~~

Cheers,
Rajiv

> -----Original Message-----
> From: Marshall Eubanks [mailto:tme@multicasttech.com] 
> Sent: Monday, March 10, 2008 4:06 PM
> To: Rajiv Asati (rajiva)
> Cc: Colin Perkins; fecframe@ietf.org
> Subject: Re: [Fecframe] Fecframe Digest, Vol 25, Issue 9
> 
> 
> On Mar 10, 2008, at 3:56 PM, Rajiv Asati (rajiva) wrote:
> 
> > Hi Colin,
> >
> > Thanks for the feedback. Could you please provide more context ?
> 
>  From the jabber logs
> 
> Colin : SAP is problematic, because its long inter-packet interval  
> interacts
> poorly with many multicast routing protocols. Have you given any
> consideration to these problems? This was the reason for the
> (stalled) IMG work in MMUSIC.
> 
> Colin : internet-media guides
> 
> Colin : Problem is that multicast state times about, because SAP  
> sends so infrequently.
> 
> [he means "times out"]
> 
> Regards
> Marshall
> 
> 
> >
> > Cheers,
> > Rajiv
> >
> >> -----Original Message-----
> >> From: Colin Perkins [mailto:csp@csperkins.org]
> >> Sent: Monday, March 10, 2008 3:39 PM
> >> To: Rajiv Asati (rajiva)
> >> Cc: Greg Shepherd; fecframe@ietf.org
> >> Subject: Re: [Fecframe] Fecframe Digest, Vol 25, Issue 9
> >>
> >> On 26 Feb 2008, at 20:06, Rajiv Asati (rajiva) wrote:
> >>> I would like to request a timeslot (15mins) to present 
> the 'FECframe
> >>> Config signaling' draft.
> >>>
> >>> 
> http://tools.ietf.org/html/draft-asati-fecframe-config-signaling-00
> >>
> >> SAP is problematic, because its long inter-packet interval 
> interacts
> >> poorly with many multicast routing protocols. Have you given any
> >> consideration to these problems? This was the reason for the
> >> (stalled) IMG work in MMUSIC.
> >>
> >> Cheers,
> >> Colin [by email, since the jabber doesn't seem to be in use]
> >>
> > _______________________________________________
> > Fecframe mailing list
> > Fecframe@ietf.org
> > https://www.ietf.org/mailman/listinfo/fecframe
> 
> 
_______________________________________________
Fecframe mailing list
Fecframe@ietf.org
https://www.ietf.org/mailman/listinfo/fecframe