OASIS Emergency Management TC

 View Only

Re: [emergency] Implementation Guide Outline

  • 1.  Re: [emergency] Implementation Guide Outline

    Posted 04-05-2004 19:10
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    emergency message

    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


    Subject: Re: [emergency] Implementation Guide Outline


    Title: Implementation Guide Outline
    Since broadcast is codec-agnostic, maybe:
     
    3 Broadcast Considerations
    3.1 Wired 
        3.1.1 Local area
        3.1.2 WAN/MAN
        3.1.3 Internet
    3.2 Terrestrial
        3.2.1 One-way
        3.2.2 Asynchronous
        3.2.3 Synchronous
    3.3 Satellite
        3.3.1 One-way
        3.3.2 Asynchronous
        3.3.3 Synchronous
    3.4 Bridging & Re-Broadcast
     
    makes more sense? Video and radio broadcast systems may use the same transport layer, and may even use the same bird. The difference between one-way and async is that async has a backchannel, but not a true two-way connection. Also since broadcast injection frequencly uses IP multicast, this is also applicable to wirelsss WAN/MAN systems and so forth, where data can be redistributed or originated (which is where bridging comes in).
     
    Cheers
    Kon