[58836] in North American Network Operators' Group
Re: About the address allocation convention between ISPs
daemon@ATHENA.MIT.EDU (Darin Wayrynen)
Tue Jun 3 02:52:18 2003
To: tfei@ipanema.ecs.umass.edu (Teng Fei)
Date: Mon, 2 Jun 2003 23:50:01 -0700 (MST)
Cc: nanog@merit.edu
In-Reply-To: <Pine.LNX.4.33.0306022337450.10423-100000@ipanema.ecs.umass.edu> from "Teng Fei" at Jun 03, 2003 01:10:33 AM
From: Darin Wayrynen <darin@deru.net>
Errors-To: owner-nanog-outgoing@merit.edu
Hi Teng,
From my experience it is standard practice for the provider of the
Internet connectivity to provide the /30 network IP addresses for
connectivity between two networks.
There are exceptions such as when using unnumbered interfaces, peering
points that share a common subnet between multiple ISPs, and when two
networks flip a coin on private peering interconnects (where generally
neither side is the provider to the other) to determine who is going
to provide the interface IPs.
Darin
>
> Hello everyone,
>
> I have a question about the convention of address allocation between ISPs.
> If a smaller ISP tries to establish connection with its provider, does
> this small ISP configure one of the interface on its boarder router using
> an IP address obtained from the provider, or it is the other way around,
> that is, the provider uses one of the IP address belongs to the customer
> to configure the provider's boarder router?
>
> I have this question because I am trying to identify the link between two
> organizations from traceroute measurements. How the addresses are
> allocated will affect the identification of the inter-domain link by
> exactly one hop.
>
> I am not sure if there is such a convention at all, or the address
> assignment is randomly decided according to the agreement between the
> customer and the provider?
>
> Since I know there are many seasoned network professionals on this mailing
> list, I think it might be a proper question to ask here. Would anyone
> kindly be willing to share your experience? Thank you very much!
>
> Sincerely
>
> Teng
>
>
>
>
