@techreport{finlayson-ttl-admin-scope-00,
    number =    {draft-finlayson-ttl-admin-scope-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-finlayson-ttl-admin-scope/00/},
    author =    {Dr. Ross Finlayson},
    title =     {{Using TTLs with Administratively Scoped IP Multicast Addresses}},
    pagetotal = 2,
    year =      1997,
    month =     mar,
    day =       26,
    abstract =  {The use of 'administratively scoped' multicast address ranges (as described in {[}1{]}) leads to a multicast traffic scoping mechanism that is superior to the original 'TTL scoping' mechanism. Contrary to popular opinion, however, administrative (often abbreviated as 'admin') scoping does not truly *replace* TTL scoping. In particular, multicast-based applications must still be aware of which TTL value(s) they use. In this document, we note that each definition of a range of admin scoped multicast addresses should be accompanied by a corresponding 'maximum effective TTL' that should be used with these addresses. We describe how these TTL values are used by applications, and how they may influence the configuration of multicast border routers.},
}