Dear sirs, I'm the tech-c contact for the it.atlanet LIR. We have planned to use pubblic IP address in order to number the point-to-point links of our customers (i.e. leased line or xDSL customers). We think that public addresses is better because it eliminates the isseus related with overlapping of private addresses that some customers could use on their LANs attached to the CPEs (the Customer Premises Equipments linked to our network via point-to-point links). Those public addresses should be unique just on each fixed access router of our backbone network. So they can be re-used in different PoPs. Of course each customer link will need 4 or 2 (if we use the RFC3021) IP addresses. Since I've noticed that the address space 169.254.0.0/16 is reserved by the IETF (RFC 3330) for the "Link Local" purpose, I was wondering which is the exactly purpose of such addresses and if could be feasible to use them to number our customer links. Anybody of you have ever used or seen the above mentioned address space being used ? What do you think if we use the 169.254.0.0/16 address space for our customer point-to-point links ? Thanks in advance for your help ! Diego Gosmar DG2617-RIPE
----- Original Message ----- From: "RIPE NCC Staff" <lir-help@ripe.net> To: "Diego Gosmar" <Diego.Gosmar@atlanet.it> Sent: Wednesday, July 16, 2003 5:32 PM Subject: Re: NCC#2003066218 IP addresses for customer WANs
Dear Diego,
On Wed, 16 Jul 2003 15:49:43 +0200, Diego Gosmar wrote: * Dear Pierre, * I've noticed today that it exists the following address space: * 169.254.0.0/16 reserved by the IETF (RFC 3330) for the "Link Local" * purpose. * It's a lot of addresses. * What do you think if we use the 169.254.0.0/16 address space for our * customer point-to-point links ? * * Thanks in advance for your help * * Diego
This sounds like a possibility. However, I couldn't find much documentation about precedents.
You could ask on the Routing Working Group mailing list. There are plenty of knowledgeable people there who might be able to help you:
http://www.ripe.net/ripe/wg/routing/index.html
Kind regards.
Pierre Baume - Hostmaster - RIPE NCC.
You can always use them on your point to point links however just be sure you do not advertise them to the internet � -----Original Message----- From: routing-wg-admin@ripe.net [mailto:routing-wg-admin@ripe.net]On Behalf Of Diego Gosmar Sent: Wednesday, July 23, 2003 11:40 AM To: routing-wg@ripe.net Subject: Link Local Addresses - RFC 3330 Dear sirs, I'm the tech-c contact for the it.atlanet LIR. We have planned to use pubblic IP address in order to number the point-to-point links of our customers (i.e. leased line or xDSL customers). We think that public addresses is better because it eliminates the isseus related with overlapping of private addresses that some customers could use on their LANs attached to the CPEs (the Customer Premises Equipments linked to our network via point-to-point links). Those public addresses should be unique just on each fixed access router of our backbone network. So they can be re-used in different PoPs. Of course each customer link will need 4 or 2 (if we use the RFC3021) IP addresses. Since I've noticed that the address space 169.254.0.0/16 is reserved by the IETF (RFC 3330) for the "Link Local" purpose, I was wondering which is the exactly purpose of such addresses and if could be feasible to use them to number our customer links. Anybody of you have ever used or seen the above mentioned address space being used ? What do you think if we use the 169.254.0.0/16 address space for our customer point-to-point links ? Thanks in advance for your help ! Diego Gosmar DG2617-RIPE
----- Original Message ----- From: "RIPE NCC Staff" < HYPERLINK
"mailto:lir-help@ripe.net"lir-help@ripe.net>
To: "Diego Gosmar" < HYPERLINK "mailto:Diego.Gosmar@atlanet.it"Diego.Gosmar@atlanet.it> Sent: Wednesday, July 16, 2003 5:32 PM Subject: Re: NCC#2003066218 IP addresses for customer WANs
Dear Diego,
On Wed, 16 Jul 2003 15:49:43 +0200, Diego Gosmar wrote: * Dear� Pierre, * I've noticed today that it exists the following address space: * 169.254.0.0/16 reserved by the IETF (RFC 3330) for the "Link Local" * purpose. * It's a lot of addresses. * What do you think if we use the 169.254.0.0/16 address space for our * customer point-to-point links ? * * Thanks in advance for your help * * Diego
�� This sounds like a possibility. However, I couldn't find much documentation about precedents.
�� You could ask on the Routing Working Group mailing list. There are plenty of knowledgeable people there who might be able to help you:
HYPERLINK "http://www.ripe.net/ripe/wg/routing/index.html"http://www.ripe.net/ripe/wg/ routing/index.html
�� Kind regards.
Pierre Baume - Hostmaster - RIPE NCC.
--- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.491 / Virus Database: 290 - Release Date: 6/18/03 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.491 / Virus Database: 290 - Release Date: 6/18/03
Hi, On Wed, Jul 23, 2003 at 12:02:25PM +0300, Wycliffe Bahati wrote:
You can always use them on your point to point links however just be sure you do not advertise them to the internet
NO! Do *NOT* use those on point-to-point links, as they will be visible in traceroutes (and other things that generate ICMPs from p2p addresses, like path mtu discovery), and sending out those ICMP packets sourced from RFC1918 addresses clearly violates the RFC. You MUST NOT send out addresses sourced from private/local addresses. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 55442 (55636) SpaceNet AG Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299
Since I've noticed that the address space 169.254.0.0/16 is reserved by the IETF (RFC 3330) for the "Link Local" purpose, I was wondering which is the exactly purpose of such addresses and if could be feasible to use them to number our customer links.
don't. by "link local" they mean what to *automatically* assign to a link when it is trying to auto-configure when there is no other choice (i.e., no manual or dhcp assignment). for example, microsoft uses it when a host can not learn its address any other way. randy
participants (4)
-
Diego Gosmar -
Gert Doering -
Randy Bush -
Wycliffe Bahati