Browse Prior Art Database

Unicast-Prefix-Based IPv4 Multicast Addresses (RFC6034)

IP.com Disclosure Number: IPCOM000200650D
Original Publication Date: 2010-Oct-01
Included in the Prior Art Database: 2010-Oct-23
Document File: 10 page(s) / 11K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Thaler: AUTHOR

Abstract

RFC 3180 [RFC3180] defines an allocation mechanism (called "GLOP") in 233/8 whereby an Autonomous System (AS) number is embedded in the middle 16 bits of an IPv4 multicast address, resulting in 256 multicast addresses per AS. Advantages of this mechanism include the ability to get multicast address space without an inter-domain multicast address allocation protocol, and the ease of determining the AS that was assigned the address for debugging and auditing purposes.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 25% of the total text.

Internet Engineering Task Force (IETF)                         D. Thaler Request for Comments: 6034                                     Microsoft Category: Standards Track                                   October 2010 ISSN: 2070-1721

              Unicast-Prefix-Based IPv4 Multicast Addresses

Abstract

   This specification defines an extension to the multicast addressing    architecture of the IP Version 4 protocol.  The extension presented    in this document allows for unicast-prefix-based assignment of    multicast addresses.  By delegating multicast addresses at the same    time as unicast prefixes, network operators will be able to identify    their multicast addresses without needing to run an inter-domain    allocation protocol.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc6034.

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Thaler                       Standards Track                    [Page 1]
 RFC 6034             Uni-Prefix-Based IPv4 Multicast        October 2010

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2    2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3    3.  Address Space . . . . . . . . . . . . . . . . . . . . . . . . . 3    4.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . . . 4    5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4    6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5    7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5    8.  Reference...