1 / 5

Efficient Hierarchical Join/Prune Attribute System for Multicast Message Format

Proposing a hierarchical scheme for optimizing multicast message format by streamlining attribute encoding. This draft introduces a more efficient method to handle attribute types and values in multicast messaging.

tcapel
Download Presentation

Efficient Hierarchical Join/Prune Attribute System for Multicast Message Format

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Hierarchical J/P attributes draft-venaas-pim-hierarchicaljoinattr-00.txt stig@cisco.com

  2. Introduction • Join attributes (should be called Join/Prune attributes) are today encoded in source addresses • For each (S,G) join/prune we can specify attributes • Think of (*,G) as a special case of (S,G) • If the same attribute type and value is to be specified for all the (S,G)s in the message, it needs to be repeated for every single (S,G) • Proposing an optional hierarchical scheme with the following properties • If an attribute type and value applies to every (S,G) in the message, only include it once in the message • Also, if an attribute type and value applies to every (S,G) for a given group G, only include it once for the group G

  3. J/P message format Each message contains a single Upstream Neighbor Address and a number of group sets Each Group Set contains a Group Address followed by lists of joined sources and pruned sources We have 3 different address objects, all in an encoded format Upstream Neighbor Address Multicast Group Address Source Address

  4. J/P Attribute Hierarchy Upstream Neighbor Address Attributes can by specified anywhere in the hierarchy. An attribute type/value applies to all the sources below 1 1 Group Address Group Address If the same type is at multiple levels, the most specific applies 2 1 Source Address Source Address Source Address Source Address 3 1 Attributes that apply to each of the sources 1 3 1 1 1 1 2 1 1 1 1

  5. Encoding types • RFC 4601 defines encoding type 0 (native), and it is used for encoded-unicast, encoded-group and encoded-source formats • RFC 5384 defines encoding type 1 (join attr) for encoded-source format • I think it makes sense to have a single encoding type space that applies to all encodings • Encoding type 1 (join attr) for all encodings would allow the described hierarchical scheme • The IANA source-encoding type registry should be turned into a common encoding type registry

More Related