This draft proposes to redefine IPv6 multicast scope 0x03 from "reserved" to "Network-Specific scope, greater than Link-Local scope, defined automatically from the network topology". The expectation is that mesh trickle multicast, as defined in draft-ietf-roll-trickle-mcast, will define multicast scope 0x03 as "all interfaces attached to links in the mesh", for use in multicast delivery.
I've requested a slot on the 6man agenda in Berlin to discuss the draft. - Ralph Begin forwarded message: > From: <internet-dra...@ietf.org> > Subject: New Version Notification for draft-droms-6man-multicast-scopes-00.txt > Date: May 22, 2013 3:15:22 PM EDT > To: Ralph Droms <rdr...@cisco.com> > > > A new version of I-D, draft-droms-6man-multicast-scopes-00.txt > has been successfully submitted by Ralph Droms and posted to the > IETF repository. > > Filename: draft-droms-6man-multicast-scopes > Revision: 00 > Title: IPv6 Multicast Address Scopes > Creation date: 2013-05-22 > Group: Individual Submission > Number of pages: 3 > URL: > http://www.ietf.org/internet-drafts/draft-droms-6man-multicast-scopes-00.txt > Status: > http://datatracker.ietf.org/doc/draft-droms-6man-multicast-scopes > Htmlized: > http://tools.ietf.org/html/draft-droms-6man-multicast-scopes-00 > > > Abstract: > This document updates the definitions of IPv6 multicast scopes. > > > > > The IETF Secretariat > -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
