[pim] IPv6 Inter-domain Multicasting and Address Assignments
"Gibbons, James" <James.Gibbons@si-intl.com> Thu, 22 February 2007 20:44 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKKnL-0007jF-Om; Thu, 22 Feb 2007 15:44:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJbnD-0006ns-7o; Tue, 20 Feb 2007 15:40:55 -0500
Received: from fw1.si-intl.com ([208.97.217.3] helo=US01EX01.si.siroot.com) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HJbnC-0007Ri-Ow; Tue, 20 Feb 2007 15:40:55 -0500
Received: from va03ex01.si.siroot.com ([10.3.0.80]) by US01EX01.si.siroot.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 Feb 2007 15:40:52 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 20 Feb 2007 15:41:33 -0500
Message-ID: <2A89D6B6FFB96046BE70561B718593F602ED6C59@va03ex01.si.siroot.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: IPv6 Inter-domain Multicasting and Address Assignments
Thread-Index: AcdVL4Jrwt8h6AVFS3+02rhe4E/ODg==
From: "Gibbons, James" <James.Gibbons@si-intl.com>
To: magma@ietf.org, pim@ietf.org
X-OriginalArrivalTime: 20 Feb 2007 20:40:52.0334 (UTC) FILETIME=[696418E0:01C7552F]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3a331e4a192f4d33f18e6f8376287cf6
X-Mailman-Approved-At: Thu, 22 Feb 2007 15:44:00 -0500
Cc:
Subject: [pim] IPv6 Inter-domain Multicasting and Address Assignments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0109720640=="
Errors-To: pim-bounces@ietf.org
Hello, SI International represents and contracts with DITO (DoD IPv6 Transition Office) on a number of IPv6 issues. In this case we are providing DITO with a white paper on IPv6 Inter-domain multicast address assignments and issues/problems (expected or realized) regarding IPv6 multicast implementations. To begin, I have gone over a number of RFCs (including RFC 3306, 3956, 3307, 2375, 4607, ID draft-ietf-mboned-ipv6-multicast-issues-02.txt among others) but they are vague as to actual working implementation of inter-domain multicast address assignments and how they will or might work proceed. I wrote to IANA and it was suggested I might contact the IEFT MAGMA and PIM groups, so I am forwarding this letter; any advice is greatly appreciated. =====my questions or issues ===== In IPv4 GLOP was developed but not widely used, where an organizations ASN is embedded in the 223.0.0.0 / 8 multicast range. In IPv6 I have seen V6UPBM (RFC 3306) and "Embedded RP" (RFC 3956) as similar proposals for IPv6. However, I am still not clear of the "reality" of IPv6 multicast address assignments especially with regards to globally unique (by organization, domain, site, etc.) inter-domain multicast. That is, how far have actual address assignments proceeded? What is just proposed versus being implemented or to be implemented? Are there actual standards being followed? Are there any referential real-world implementations? Are there known/expected issues/problems with IPv6 inter-domain multicast and address assignments? Maybe a quote from my actual assignment will further clarify what I am looking for: "DITO is having some concerns with IPv6 multicast address space and how it should or should not be provisioned. You should start the study with regards to how IPv4 multicast addressing worked in the past. If you ever worked with it you would know there was never official group reservations made with regards to address blocks. However, this was never a real issue since its popularity died. So except for what was deemed to be the well-known addresses there was never any reservations, unlike how unicast is reserved. One thought might be the Army gets a block of addresses, Navy, and so on." =============== Again, any help is appreciated. Thanks, James Gibbons Senior Network Engineer SI International Tel: 703.234.6894
_______________________________________________ pim mailing list pim@ietf.org https://www1.ietf.org/mailman/listinfo/pim
- [pim] IPv6 Inter-domain Multicasting and Address … Gibbons, James
- Re: [pim] IPv6 Inter-domain Multicasting and Addr… Tim Chown