Re: You asked about multicast scope

Kerry Lynn <kerlyn@ieee.org> Thu, 29 March 2012 10:39 UTC

Return-Path: <kerlyn2001@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CED3521F8890; Thu, 29 Mar 2012 03:39:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.951
X-Spam-Level:
X-Spam-Status: No, score=-102.951 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9zMPf4d3+Ztv; Thu, 29 Mar 2012 03:39:09 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7FCA721F887D; Thu, 29 Mar 2012 03:39:08 -0700 (PDT)
Received: by lagj5 with SMTP id j5so2740677lag.31 for <multiple recipients>; Thu, 29 Mar 2012 03:38:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=fmeJKMiYuIzPEF6pD4RU7OzNKvpaKA6ygZzS+vcoJrk=; b=kWTH8hajyyOAOi1cAewpMsazbsvHLvyskl0zhJSOpL5M1DFtdgTCjsD9yoy+7QsV08 aTimzqD4HlUrTF3xhhsK11IwxtZvHPiEZIz+TE70NPVY7jVy9N3GFFd2pWx6GM0N6jyl ir69+rP5J08dOJVaMqeov5cFMbXhm5KM8Pk5PRrFi0QzZd2MgDHzWyUtTr5N8FxlJXJJ 95zLN3RvBzqzqDQpj0EFxG7c32v8HpHY5Zww1QNVUGFopGYUyKZ/5XozdIXp4+UA4p8B 7xHbYOOBz9Uq0QvigDDZA8bStd382GePz62vDouo/56jcpvdVt/FHzU+SBjwhoTXZfYS vSaw==
MIME-Version: 1.0
Received: by 10.152.115.38 with SMTP id jl6mr27404776lab.24.1333017535020; Thu, 29 Mar 2012 03:38:55 -0700 (PDT)
Sender: kerlyn2001@gmail.com
Received: by 10.112.77.179 with HTTP; Thu, 29 Mar 2012 03:38:54 -0700 (PDT)
In-Reply-To: <848F4FFF-2303-4E49-81CB-A0BD9180F31D@muada.com>
References: <FF493C74-28AA-4B3D-ABBA-38294010230F@cisco.com> <BEEE8260-1AC5-41C9-A9D7-EFF1CCF5CBB4@muada.com> <DA8DC604-C36C-4D59-931A-B7C22F8E2051@cisco.com> <00B02ED4-4D6F-4B67-B548-D186C1B3B2CA@muada.com> <2AA4DD9C-DD38-422C-8483-FF295C086E11@cisco.com> <848F4FFF-2303-4E49-81CB-A0BD9180F31D@muada.com>
Date: Thu, 29 Mar 2012 12:38:54 +0200
X-Google-Sender-Auth: KfHYk_qfKrUYVLUApbejnqSWXzI
Message-ID: <CABOxzu0yC6Y4gFXKACDSdAy+GNzWGZStjpVMUB5HWXjBoXKUxw@mail.gmail.com>
Subject: Re: You asked about multicast scope
From: Kerry Lynn <kerlyn@ieee.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: multipart/alternative; boundary="f46d040891eba77ce304bc5f5455"
Cc: pcp@ietf.org, 6man 6man <ipv6@ietf.org>, Fred Baker <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 10:39:09 -0000

On Thu, Mar 29, 2012 at 12:02 PM, Iljitsch van Beijnum
<iljitsch@muada.com>wrote:

> On 28 Mar 2012, at 12:08 , Fred Baker wrote:
>
> >> I haven't read the spec yet, but isn't PCP supposed to work in the
> service provider run NAT64/CGN case, too? In that case, the multicasts need
> to escape out of the site or even organization to reach the service
> provider at least in the SOHO case. So this would be a scope just shy of
> global, maybe a new "service provider" scope?
>
> > I personally rarely use "zero configuration" and "service provider" in
> the same sentence...
>
> Am I understanding you correctly when I take that to mean that the admin
> (value 4) scope is appropriate because then the people running the
> multicast routing can determine exactly how far these packets travel?
>
> That makes sense, but there is one potential issue, that I think some
> people who are well-steeped in IPv6 multicast should look at: in this
> situation, the scope value 4 may need wider distribution than side-wide,
> which is scope 5. I can't find any documentation on whether that's ok or
> not between sessions right now, but I'm reluctant to assume that a lower
> scope value can have wider distribution than a higher one without having a
> spec that explicitly says so or hearing from some implementers.
>
> Correct me if I'm wrong, but isn't Admin Scoped multicast defined on a per-
port, per-application basis?  That would suggest that some multicast group
addresses can (selectively) be forwarded through the CER uplink to the ISP.

-K-

Iljitsch
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>