Re: [Bier] Questions on draft-eckert-bier-te-arch-01

Study the architecture document for distinction between SI and subdomain. 

SIs are a concept to fit more than BSL of BFERs into a subdomain. 

A subdomain is something where you map a service on so you achieve separation or can separate clusters of receivers from each other. Each subdomain may follow a different topology, carry different type of service, use different assignment of BFR-ids and with that has a different distribution tree possibly. 

If you can play tricks with assignments to fit them into same SI, you are basically using SIs in a sense as sub-domain. This is maybe OK for you but won't work well if you need e.g. service speration in terms of scheduling or receivers joining/leaving subdomains and want to separate a subdomain from the impact of another subdomain. 

BIER is an architecture, not a 'multicast cookbook'. We kept it quite generic to allow for all kind of unexpected applicatons as you have it and give you simply a box of tools like SI, MT, subdomains to allow for mapping of your architectural entities into BIER abstractions to fit your needs  ... 

Thanks 

--- tony 

There are basically two types of people. People who accomplish things, and people who claim to have accomplished things. The first group is less crowded.
~~~ Mark Twain

> -----Original Message-----
> From: BIER [mailto:bier-bounces@ietf.org] On Behalf Of Caitlin Bestler
> Sent: Friday, October 09, 2015 9:25 AM
> To: bier@ietf.org
> Subject: Re: [Bier] Questions on draft-eckert-bier-te-arch-01
> 
>  From a usage perspective SIs and sub-domains can be fairly interchangeable.
> For my storage application I shifted from mapping groups of storage servers
> from being sub-domains to assigning their IDs so they had the same SI.
> 
> So I can easily see an argument for eliminating one of them.
> 
> But why the SI rather than the sub-domain?
> 
> Is there a summary of their difference from both the implementation and usage
> perspectives?
> 
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier