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

Colin Perkins <csp@csperkins.org> Tue, 11 March 2008 10:35 UTC

Return-Path: <fecframe-bounces@ietf.org>
X-Original-To: ietfarch-fecframe-archive@core3.amsl.com
Delivered-To: ietfarch-fecframe-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 36E4E3A6D81; Tue, 11 Mar 2008 03:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.686
X-Spam-Level:
X-Spam-Status: No, score=-100.686 tagged_above=-999 required=5 tests=[AWL=-0.249, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HyQASpkIDqw3; Tue, 11 Mar 2008 03:35:56 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EB8228C2C6; Tue, 11 Mar 2008 03:35:56 -0700 (PDT)
X-Original-To: fecframe@core3.amsl.com
Delivered-To: fecframe@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D62AF3A6D86 for <fecframe@core3.amsl.com>; Tue, 11 Mar 2008 03:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ImXGjs7+J4dF for <fecframe@core3.amsl.com>; Tue, 11 Mar 2008 03:35:50 -0700 (PDT)
Received: from mr1.dcs.gla.ac.uk (mr1.dcs.gla.ac.uk [130.209.249.184]) by core3.amsl.com (Postfix) with ESMTP id 823EC3A6D81 for <fecframe@ietf.org>; Tue, 11 Mar 2008 03:35:50 -0700 (PDT)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:54904) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42) id 1JZ1nV-0007fl-CX; Tue, 11 Mar 2008 10:33:29 +0000
In-Reply-To: <15B86BC7352F864BB53A47B540C089B6050FF5C4@xmb-rtp-20b.amer.cisco.com>
References: <15B86BC7352F864BB53A47B540C089B6050FF5C4@xmb-rtp-20b.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <82E62DB5-217C-4795-9100-50C24CB3E363@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
Date: Tue, 11 Mar 2008 10:33:38 +0000
To: Rajiv Asati <rajiva@cisco.com>
X-Mailer: Apple Mail (2.753)
Cc: fecframe@ietf.org
Subject: Re: [Fecframe] Fecframe Digest, Vol 25, Issue 9
X-BeenThere: fecframe@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of FEC Framework <fecframe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/fecframe>, <mailto:fecframe-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/fecframe>
List-Post: <mailto:fecframe@ietf.org>
List-Help: <mailto:fecframe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fecframe>, <mailto:fecframe-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: fecframe-bounces@ietf.org
Errors-To: fecframe-bounces@ietf.org

Rajiv,

The problem isn't the adaptation, it's the length of the interval.
Colin


On 10 Mar 2008, at 20:15, Rajiv Asati (rajiva) wrote:
> 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



-- 
Colin Perkins
http://csperkins.org/


_______________________________________________
Fecframe mailing list
Fecframe@ietf.org
https://www.ietf.org/mailman/listinfo/fecframe