IETF Logo Mail Archive

Re: [ssm] msnip status

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

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESXLj-0004n6-CQ; Thu, 20 Oct 2005 06:08:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESXLh-0004mV-M6; Thu, 20 Oct 2005 06:08:37 -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 GAA28973; Thu, 20 Oct 2005 06:08:28 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESXXb-00024r-TK; Thu, 20 Oct 2005 06:20:57 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 20 Oct 2005 03:08:27 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.97,235,1125903600"; d="scan'208"; a="13534894:sNHT21244696"
Received: from [192.168.1.4] (che-vpn-cluster-2-123.cisco.com [10.86.242.123]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j9KA8MEi024878; Thu, 20 Oct 2005 06:08:23 -0400 (EDT)
Message-ID: <43576C95.6080403@cisco.com>
Date: Thu, 20 Oct 2005 03:08:21 -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: Pekka Savola <pekkas@netcore.fi>
Subject: Re: [ssm] msnip status
References: <20051019124841.GL9025@storhaugen.uninett.no> <ce8f3212bc8ba11a7739b4c9433e3a22@innovationslab.net> <20051019231203.GG29643@cisco.com> <Pine.LNX.4.61.0510201201450.27313@netcore.fi>
In-Reply-To: <Pine.LNX.4.61.0510201201450.27313@netcore.fi>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Cc: Toerless Eckert <eckert@cisco.com>, magma@ietf.org, 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

Pekka Savola wrote:
> Could you elaborate a bit on what you think is this "key functionality" 
> and why exactly it's "key" (e.g., specific scenarios you have in mind)?

As I believe was described in the draft MSNIP is important in the case 
where you have a server with a very large number of potential sessions 
but only a small number of active sessions. So if the server has content 
available on 1000 different groups and there are active receivers at any 
time only for 10 of them, the box / link you would need to drive this 
with and withhout MSNIP is totally different.

Isidor

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

v2.23.0 | Report a Bug | By Email