HOBBIT = High Order Bytes and BITs The prefix allocated directly to an operator by an RIR.
Brian Michel Py wrote: > > > Pekka Savola wrote: > > Or perhaps you should describe in detail what the term would > > be useful for in this context? > > There different things involved: > > - Allocation policies, which is "We give a /32 to Joe for this reason and a /35 to >Jane for that reason". > > - Aggregation policies, which is "All networks matching criteria xyz must aggregate >at the /xx boundary". > > - Addressing architecture, which does not define how to do it but what is is. > > The point I am trying to make here is that we need a name or acronym for "ISPs that >receive their addresses directly from a RIR". I am not saying that "TLA" is the best >definition, but it does fit, regardless of allocation policies and aggregation >policies. > > There was a reason it was defined in RFC2373 and the changes to >draft-ietf-ipngwg-addr-arch-v3-07.txt have not changed this, AFAIK. > > I am not proposing to define "TLA" or whatever we come up with as an aggregation >policy, but as the concept of ISPs that receive their blocks directly for a registry. >How big the block they get is an allocation policy issue, where they aggregate is an >aggregation policy issue, who they are is an addressing architecture issue. > > Michel. > > -------------------------------------------------------------------- > IETF IPng Working Group Mailing List > IPng Home Page: http://playground.sun.com/ipng > FTP archive: ftp://playground.sun.com/pub/ipng > Direct all administrative requests to [EMAIL PROTECTED] > -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
