SSM working group minutes
March 2001 IETF Minneapolis, MN
-----------------------------
Updates on existing ssm drafts
holbrook-ssm-arch 02
Hugh Holbrook gave update
Addressed ipv6
Added examples and address range
Ready for wg last call for proposed standard
bhattach-pim-ssm
Supratik gave update
Added IPv6 and security discussion
Remaining: conformance with the architecture
Headed for informational
Need comments
holbrook-idmr-igmpv-v3-ssm-01
Hugh Holbrook gave update
New changes
IGMP module should have configuration option for
SSM ranges
Default to IANA range
Must allow for manual config
IGMPv3 hosts MUST not transition to exclude mode when it runs out of resources. Now in base igmpv3 spec.
This doc will move to new MAGMA working group should it be approved.
He-mixed-igmp-proxy
He gave update
Current igmp proxying draft only addresses behavior for same version proxying
With mixed versions, there are some differences :
v3 to v2 - v2 on upstream, v3 on downstream
v3 joins translated to v2 joins forwarding is still done based on v3 info
v2 to v3 - proxy should drop v2 joins in ssm range
Hugh pointed out that faking v3 when you have v2 upstream routers is a configuration bug.
Dave Thaler gave an example of where proxy must look at source address and not just transparently send upstream to router when source is not toward router.
Hal Sandick would like to see transition section updated before last call.
draft-kim-ssm-hierarchical-scheme-00
Myung-ki Shin talked about their draft
SSM ignores deployment issues in inter-domain
Hierarchical considerations should be considered
Automatic tunneling between border gateway and source not on multicast network
Receiver requirements
no changes required
Border gateway router requirements
sends unicast registration to source
Source requirements
source receives registration message and tunnels
ssm data to all border gateway routers
Dave Meyer
Suggested that SSM doesn't have a scaling problem.
Concerned that this draft solves a problem we don't have consensus that this is an incremental deployment solution that should be discussed in MBONED.
DNS for SSM
Hugh summarized discussion on mailing list
Jeff Schoch :
mcast.example.com IN A 10.10.10.42
radio.mcast.example.com IN A 232.1.1.1
Dino :
radio.example.com IN AA
10.1.1.1.232.1.1.1
Toerless :
just use SDP
draft-schoch-dns-ssm :
Jeff Schoch gave a talk on his proposal :
Little change to existing infrastructure, keep it simple
Proposal: group.source.domain-name
Joel objected to this method : doesn't give you the info you really need. SDP does have all the info you need, not just the IP addresses.
Dave Thaler agreed with Joel
Hugh repeated that on the mailing list it was mentioned that this might be useful for debugging.
Dave Meyer did not like the idea of putting semantic context in the DNS.
Off topic, Dave would like us to use ASM (Any source multicast) instead of
ISM (Internet standard multicast)
Ross Finlayson said use
SIM (source independent multicast)
Hugh polled the working group on AA records.
Dave Meyer still objected.
Joel said while people may want a replacement for SDR, we don't really need one. Multicast is no different than unicast in this sense.
Hugh said others thought it might be useful for mtrace
Marshall didn't think it was ever useful to have names to map to group and source.
Jeremy Hall said that people with access to sources aren't the same people with access to DNS.
No conclusion reached, the discussion is to be taken to the mailing list.
Charter Bashing
Charter item have been fulfilled.
There are no new action items
We expect this is the last meeting.
