Re: [ssm] msnip status

Isidor Kouvelas <kouvelas@cisco.com> Thu, 20 October 2005 07:51 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESVCw-0005XQ-Uz; Thu, 20 Oct 2005 03:51:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESVCv-0005XG-12 for ssm@megatron.ietf.org; Thu, 20 Oct 2005 03:51:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22469 for <ssm@ietf.org>; Thu, 20 Oct 2005 03:51:14 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESVOn-0006DA-0E for ssm@ietf.org; Thu, 20 Oct 2005 04:03:43 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 20 Oct 2005 03:51:14 -0400
X-IronPort-AV: i="3.97,235,1125892800"; d="scan'208"; a="74070855:sNHT25317820"
Received: from [192.168.1.4] (che-vpn-cluster-2-123.cisco.com [10.86.242.123]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j9K7p923029662; Thu, 20 Oct 2005 03:51:10 -0400 (EDT)
Message-ID: <43574C67.6050409@cisco.com>
Date: Thu, 20 Oct 2005 00:51:03 -0700
From: Isidor Kouvelas <kouvelas@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Toerless Eckert <eckert@cisco.com>
Subject: Re: [ssm] msnip status
References: <20051019124841.GL9025@storhaugen.uninett.no> <ce8f3212bc8ba11a7739b4c9433e3a22@innovationslab.net> <20051019231203.GG29643@cisco.com>
In-Reply-To: <20051019231203.GG29643@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: 7bit
Cc: Brian Haberman <brian@innovationslab.net>, ssm mailing list <ssm@ietf.org>
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=subscribe>
Sender: ssm-bounces@ietf.org
Errors-To: ssm-bounces@ietf.org

FWIW I do not think that dropping the MRD option was a show stopper for 
MSNIP. The reason the work stalled was that there was no interest. I 
agree with Toerless that it was a key piece for SSM.

Isidor

Toerless Eckert wrote:
> Brian: What exactly where the points that stopped the last MSNIP draft
> from moving forward ? I unfortunately don't remember the details,
> and in general i'm of course annoyed that there's no good means in the
> IETF to keep that last work status summary alive in case it needs to
> get picked up again.
> 
> I think MSNIP tried to solve a key functionality for the SSM architecture,
> and while it may be possible to ad-hoc hack something similar up once
> somebody requires it, i still think that it would be good to have an
> IETF recommendation for this functionality.
> 
> If we were to release an RFC, we could make it informational. I don't
> think that MSNIP itself needs to be focussed on what Pekka is claiming
> "universal adoption". Because it only applies to sources, it will always
> tender only to comparably much fewer places than for example IGMP. 
> 
> Cheers
> 	Toerless
> 
> 
> On Wed, Oct 19, 2005 at 12:40:30PM -0400, Brian Haberman wrote:
> 
>>Hi Stig,
>>     The consensus is that msnip is not the solution people want.
>>Additionally, there has been no one volunteering to work on the
>>problem in general.
>>
>>     Combining MSNIP with MRD doesn't make a lot of sense
>>and any such plans were abandoned.
>>
>>     If you have people interested in the problem, have them bring
>>forth ideas.
>>
>>Regards,
>>Brian
>>
>>On Oct 19, 2005, at 8:48, Stig Venaas wrote:
>>
>>
>>>Now that magma is being shut down, what is the future of
>>>draft-ietf-magma-msnip? I know several people that are
>>>interested in seeing this work continue. Are there any
>>>plans for that, or has it more or less been decided that
>>>this is not the way to go? I know there were discussions
>>>on combining it with MRD, but don't think that went
>>>anywhere.
>>>
>>>Stig
>>>
>>>
>>>_______________________________________________
>>>ssm mailing list
>>>ssm@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/ssm
> 
> 
> 
> 
>>_______________________________________________
>>ssm mailing list
>>ssm@ietf.org
>>https://www1.ietf.org/mailman/listinfo/ssm
> 
> 
> 

_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm