Re: [MBONED] WGLC for <draft-ietf-mboned-ipv4-uni-based-mcast-04.txt>

Tim Chown <tjc@ecs.soton.ac.uk> Tue, 22 January 2008 15:05 UTC

Return-path: <mboned-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHKh4-0003hW-L1; Tue, 22 Jan 2008 10:05:42 -0500
Received: from mboned by megatron.ietf.org with local (Exim 4.43) id 1JHKh3-0003hR-8l for mboned-confirm+ok@megatron.ietf.org; Tue, 22 Jan 2008 10:05:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHKh0-0003gM-Lx for mboned@ietf.org; Tue, 22 Jan 2008 10:05:38 -0500
Received: from owl.ecs.soton.ac.uk ([2001:630:d0:f102:230:48ff:fe77:96e]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHKh0-0004Xa-7Y for mboned@ietf.org; Tue, 22 Jan 2008 10:05:38 -0500
X-ECS-MailScanner-Watermark: 1201619120.48704@rzR5pwQjtRUPexdzBbGUug
Received: from goose.ecs.soton.ac.uk (goose.ecs.soton.ac.uk [IPv6:2001:630:d0:f102:230:48ff:fe78:67b5]) by owl.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id m0MF5K6G026580 for <mboned@ietf.org>; Tue, 22 Jan 2008 15:05:20 GMT
X-ECS-MailScanner-Watermark: 1201618823.09031@yssh9qYYqD1yE24Ju80AcQ
Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk [IPv6:2001:630:d0:f102:230:48ff:fe59:5f12]) by goose.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id m0MF0Mc1004715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mboned@ietf.org>; Tue, 22 Jan 2008 15:00:22 GMT
Received: from login.ecs.soton.ac.uk (localhost.localdomain [127.0.0.1]) by login.ecs.soton.ac.uk (8.13.8/8.11.6) with ESMTP id m0MF5ANq005762 for <mboned@ietf.org>; Tue, 22 Jan 2008 15:05:10 GMT
Received: (from tjc@localhost) by login.ecs.soton.ac.uk (8.13.8/8.13.8/Submit) id m0MF5AGu005761 for mboned@ietf.org; Tue, 22 Jan 2008 15:05:10 GMT
Date: Tue, 22 Jan 2008 15:05:10 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: mboned@ietf.org
Subject: Re: [MBONED] WGLC for <draft-ietf-mboned-ipv4-uni-based-mcast-04.txt>
Message-ID: <20080122150510.GL22077@login.ecs.soton.ac.uk>
References: <26945.1201000836@aber.ac.uk> <758A010F-C191-4CFB-A664-F10183B44BDD@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <758A010F-C191-4CFB-A664-F10183B44BDD@cisco.com>
User-Agent: Mutt/1.4.2.2i
X-ECS-MailScanner: Found to be clean, Found to be clean
X-Spam-Status: No
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-Spam-Score: -1.4 (-)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
Errors-To: mboned-bounces@ietf.org

On Tue, Jan 22, 2008 at 04:51:39AM -0800, Dino Farinacci wrote:
> >tjc@ecs.soton.ac.uk said:
> >>It's all very well to try to block this draft on a point of  
> >>principle,
> >>but the reality is that there are issues deploying SSM today, and in
> >>getting globally scoped group addresses for ASM.
> >
> >>I would in fact probably argue that in order to give multicast a foot
> >>up in general, getting initial services running with ASM, until SSM  
> >>is
> >>ready, could potentially be very useful.
> >
> >I've been quietly reading all the emails going
> >past on this issue.   I too can see the "point of principle",
> >but I, like Tim and others, really do think we need
> >something that will work in the short to medium
> >term for ASM.
> 
> Can you two be a little more specific. Are you saying the network  
> layer or multicast protocols need to do more (or less) and if so, what  
> do you think they need to do.

I can't speak for Dave, but in my view its 

a) global scope group addresses for end sites to use.   This is problematic
   today for certain scenarios.   But obviously I can only speak with the
   knowledge of the community I'm in (from various BoFs etc we have had).

b) tools to allow applications to determine available addresses within
   the site.   This arises from researchers and students writing (often 
   but not always IPv6) multicast applications.    There's madcap but...

I think the draft answers a) sufficently well for the short to medium
term (beyond which SSM will maybe get more uptake), while b) is a topic
I raised at IETF69(?) and on which I think there was a new draft posted 
quite recently.

-- 
Tim




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