Re: You asked about multicast scope

Iljitsch van Beijnum <iljitsch@muada.com> Thu, 29 March 2012 10:02 UTC

Return-Path: <iljitsch@muada.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 9E36421F87CB; Thu, 29 Mar 2012 03:02:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 qItYPN3koyCU; Thu, 29 Mar 2012 03:02:53 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id DEEB021F87C7; Thu, 29 Mar 2012 03:02:52 -0700 (PDT)
Received: from [IPv6:2001:df8::16:d9d6:7795:a05d:df7f] ([IPv6:2001:df8:0:16:d9d6:7795:a05d:df7f]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id q2TA2U6I095722 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 29 Mar 2012 12:02:31 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: You asked about multicast scope
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset="us-ascii"
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <2AA4DD9C-DD38-422C-8483-FF295C086E11@cisco.com>
Date: Thu, 29 Mar 2012 12:02:46 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <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>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1257)
Cc: pcp@ietf.org, 6man 6man <ipv6@ietf.org>
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:02:53 -0000

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.

Iljitsch