Keith Moore wrote:
So, as I wrote in this forum about a week ago, what I'd like
to see in that area is simply provider independant, registry
allocated, easy accessible (very low registry fees, no question
asked) public address space, and then forget about the scope
discussion
Brian,
Michel Py wrote:
Because then the addresses used on the private network would be
routable PI, which is exactly what network designers don't want
when they design a private network with private addresses.
Brian Carpenter wrote:
I still don't understand the difference between using a
On Tue, 12 Aug 2003 12:09:20 -0700
Michel Py [EMAIL PROTECTED] wrote:
Routing it over the Internet (without a VPN) for inter-entrerprise
communication would also be perfectly legitimate, host-to-host IPSEC for
example. Then the line between it and global PI ceases to exist.
I think a
Possibly naive, but I'm not convinced that leaking local addresses for PI
purposes is that big a problem.
Assumptions (as specified by H/H draft):
(1) Most (all compliant) trunk routers will not route local packets. Most
(all compliant) border routers will not route local packets. Some
On Thu, 14 Aug 2003 13:29:15 +0200
Brian E Carpenter [EMAIL PROTECTED] wrote:
I almost agree, except that I would insist on no cost.
Low cost is often impossible, since that even a base charge
for $0.50 requires invoicing across several continents and
purchasing departments and levels
So, as I wrote in this forum about a week ago, what I'd like
to see in that area is simply provider independant, registry
allocated, easy accessible (very low registry fees, no question
asked) public address space, and then forget about the scope
discussion which is an
Hi Michel,
At 12:09 PM 8/12/2003 -0700, Michel Py wrote:
- Whatever we can say about it, the network administrator gets to pick
what becomes of the Hinden/Haberman draft, globally routable PI _or_
private address. The prefix can't serve both purposes at the same time
for reasons explained 20
Brian E Carpenter wrote:
What you refuse to acknowledge is that there is a high probability that
the Hinden/Haberman draft will be misused as globally routable PI.
There's a 100% probability it will be used for inter-enterprise
routing (i.e. exceptions such as VPNs to normal routing).
A considered reply to a couple of postings:
Under the subject RE: site-local observations from the outside
Michel Py wrote:
Brian,
Michel Py wrote:
It's a matter of risk: If I use the
Hinden/Haberman draft as private addresses, and if it ends up
being perverted as PI, my entire
Hello Alain,
Alain Durand wrote:
So, as I wrote in this forum about a week ago, what I'd like
to see in that area is simply provider independant, registry allocated,
easy accessible (very low registry fees, no question asked)
public address space, and then forget about the scope discussion
10 matches
Mail list logo
