>Yes, a book on operational Internet routing issues would be great.
>For example, what is SWIP? What is a route registry? In fact, could
>you answer those questions here?? ;-)
>
>Priscilla
Starting points on both:
SWIP
----
SWIP is the Shared Whois Project, which is the means of tracking who
has been assigned what address block. In contrast to the main
registries at ARIN, RIPE, and APNIC (with more registries such as
LACNIC coming for Latin America), which track the _allocation_ of
provider-independent address space, SWIP goes to the next level and
tracks the _assignment_ of sub-blocks of provider assigned address
space to provider customers.
ARIN template instructions: http://www.arin.net/regserv/templates/instr.html
the SWIP template itself http://www.arin.net/templates/swiptemplate.txt
Cable & Wireless' script for generating SWIP requests, which is informative:
http://infopage.cary.cw.net/IP_Addressing/2)_Address_Request_Templates
/swip.html
somewhat dated, but thoroughly readable: http://www.dx.net/swip.html
Routing Registries
------------------
There's an urban legend that BGP transmits policies. More correctly,
BGP carries information that can be used in making policy decisions,
but the policies themselves are not explicitly carried by BGP.
It is possible to write down policies, however, and the best current
practice for doing so is the Routing Policy Specification Language
(RPSL). See RFC 2622 for the language specification and RFC 2650 for
an operational use tutorial.
Policies written in RPSL are stored in a distributed database called
the Routing Arbiter Data Base (RADB). See http://www.radb.net and
http://www.arin.net/routingreg/faq.html In principle, each AS
records its external routing policies in the RADB. In practice, it
is optional to do so, and some AS do not list private peering
information. A wide variety of public domain tools for configuration
and troubleshooting run off RADB definitions.
Routing registries are organized by AS number, but are above and
beyond the AS number and address space assignments by address
registries. Real-world internet operations involves interactions
among AS, routing policies, address assignments, and DNS.
>
>
>At 10:44 AM 7/25/00, Howard C. Berkowitz wrote:
>>This is a good question, and I'd like to pose a question myself to
>>people who read my response. As far as I am concerned, my answers
>>here are at the minimum real-world level for Internet routing
>>operations. I draw a distinction between Internet routing
>>operations and "BGP".
>>
>>ACRC was completely useless, IMNSHO, when it came to BGP and the
>>wider subject of Internet routing operations. There's a lot of
>>discussion about a new emphasis on BGP in BCSN. From talking to
>>some BCSN instructors, however, my sense is that the operational
>>issues I describe below are _not_ considered in the courseware. Am
>>I correct in that assumption?
>>
>>Do some current instructors go beyond that level in chalktalks or
>>supplementary materials?
>>
>>Aside from personal curiosity and planning the next BGP paper for
>>CertZone, I have the ulterior motive of writing a proposal for an
>>Internet Routing book, that is more operational-environment, less
>>configuration and protocol mechanics oriented than the books out
>>there now. It would also be multivendor (Cisco, gated/rsd, Bay RS,
>>JunOS). I'm trying to figure out if these are problems I should
>>write a book to solve.
>>
>>
>>>I trying to add redundency to my network at work (I work for a very small
>>>local ISP) and I'd like to run BGP on this router so that if line A dies to
>>>upstream provider A, line B will take over to upstream provider B.
>>>
>>>What is the least requirement for BGP? Someone told me I needed at least a
>>>/20 of IP's from ARIN. Someone else told me that I need SWIP instead of
>>>RWHOIS. So I'm left wondering exactly what is the minimum overall
>>>requirements to run BGP?
>>
>>BGP itself does not have any minimum requirement. A decreasing
>>number of major ISPs, however, filter routes longer than /19 or /20.
>>
>>If you are homed to at least two upstream providers, with at least
>>T1 speed, you can generally justify your own AS number. That
>>assignment is independent of your address space; you do not
>>necessarily need provider-independent address space to get a
>>registered AS.
>>
>>When requesting an AS, expecting to advertise provider-assigned
>>space, you will probably need to document that the provider that is
>>assigning you the address space will advertise your more-specific
>>assignment as well as their supernet. You will also need to
>>document that your alternate provider will advertise this same
>>more-specific block assigned to your primary provider, and the
>>primary provider consents to the alternate provider advertising it.
>>All this should be recorded in a route registry as well as in the
>>AS number application.
>>
>>As far as the address space, there is a "fast start" procedure at
>>ARIN. If an ISP can demonstrate efficient use of a /21, and is
>>growing, it can request a "fast start" /20. This /20 will be one
>>half of a /19, and you are permitted to advertise the /19 to get
>>through prefix length filters. You have to agree to justify the
>>full /19 in 18 months, or renumber back into provider assigned
>>space.
>>
>>Yes, I would agree SWIP is far more widely used than RWHOIS. Check
>>with ARIN if RWHOIS is acceptable for documenting your address
>>assignments. SWIP and DNS are part of your routing/address
>>management.
>
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
