[ssm] Re: your mail

Toerless Eckert <eckert@cisco.com> Thu, 17 July 2003 14:27 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09028 for <ssm-archive@lists.ietf.org>; Thu, 17 Jul 2003 10:27:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d9in-0004FT-7X; Thu, 17 Jul 2003 10:27:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d9hu-0004FA-Rs for ssm@optimus.ietf.org; Thu, 17 Jul 2003 10:26:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08989 for <ssm@ietf.org>; Thu, 17 Jul 2003 10:26:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19d9hs-0006mH-00 for ssm@ietf.org; Thu, 17 Jul 2003 10:26:04 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 19d9hh-0006lo-00 for ssm@ietf.org; Thu, 17 Jul 2003 10:25:54 -0400
Received: from cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 17 Jul 2003 07:29:41 -0700
Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h6HEOruJ015918; Thu, 17 Jul 2003 07:24:53 -0700 (PDT)
Received: (from eckert@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id HAA26819; Thu, 17 Jul 2003 07:24:53 -0700 (PDT)
Date: Thu, 17 Jul 2003 07:24:53 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Dino Farinacci <dino@procket.com>
Cc: hoerdt@clarinet.u-strasbg.fr, mboned@network-services.uoregon.edu, ssm@ietf.org
Message-ID: <20030717142453.GC23110@cypher.cisco.com>
References: <Pine.LNX.4.56.0307171118550.22244@clarinet.u-strasbg.fr> <200307171407.h6HE7doV015276@dino-pc.procket.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200307171407.h6HE7doV015276@dino-pc.procket.com>
User-Agent: Mutt/1.4i
Subject: [ssm] Re: your mail
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
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>

On Thu, Jul 17, 2003 at 07:07:39AM -0700, Dino Farinacci wrote:
> >> So, What is missing from IPv4 SSM today apart from a deployment effort
> >> today ?
> 
>     Nothing.

Ok, let's see if you would consider all of the below to be deployment.
I would consider most of this to be development, not deployment. Anyhow,
the list isn't short.

Technologies:

- Source redundancy solutions for SSM channels.

- Check wether all transport/session and higher level IETF specifications
  that carry group addresses can also carry source addresses (eg:
  SDP source filter extensions). Finalization of RTCP for SSM solutions. 

Standards:

- A good understanding how to do SSM within other than the global
  scope (eg: something like an informational recommendation on how
  to do SSM within 239/8)

- A nice application side solution (standard, + freely available implementation)
  to emulate ASM on top of SSM. The final goal for that would be something like:
  put that emulation into OS kernels so that ASM applications do not need
  to be modified.

- Finalization of all open drafts into RFCs so that anybody working
  on actual standards basedd application solutions can start to use SSM.
  Hint: Standards based application solutions tend to NOT refer to
  any technologies unless they are specified in finalized documents,
  eg: RFCs (see discussions in DVB or other application organizations -
  if that's how it can be called).

Development:

- Lots of key implementations:
  - IGMPv3 support in switches, both basic and full IGMPv3 snooping
    (basic is a term i use for per-MAC address filtering, whereas
     full IGMPv3 snooping does per (S,G) IP address filtering).
  - IGMPv3 host stacks: MacOS, Set Top Boxes, Solaris
  - Any commercial applications beside WIndows Media and IP/TV
    (what other commercial applications support SSM ?) No EPG software
    in STBs supports SSM, 
  - Implementations of IGMPv3 router side in router vendors
    other than C,J,P - does N support it ? How about E and F ? ...

Deployment wise (as i define deployment):
  - Waiting for more than 40% of users to migrate to OSs supporting 
    IGMPV3/SSM.
  - Persuading enterprise networks to consistently upgrade edge routers
    to enable IGMPv3.

And this all does not cover transition solutions that may be necessary
to move forwards faster than being blocked on any of these problems.

Cheers
	Toerless

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