This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] Reopening discussion on RIPE Policy Proposal 2006-05
- Previous message (by thread): [address-policy-wg] Reopening discussion on RIPE Policy Proposal 2006-05
- Next message (by thread): [address-policy-wg] Reopening discussion on RIPE Policy Proposal 2006-05
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stream Service || Mark Scholten
mark at streamservice.nl
Sun Jul 26 00:47:21 CEST 2009
Hello Jeroen, It was a reaction based on the message Per did write. If you compare IP addresses to phone numbers: compare everything and not just the part you like. With kind regards, Mark Scholten -----Original Message----- From: address-policy-wg-admin at ripe.net [mailto:address-policy-wg-admin at ripe.net] On Behalf Of Jeroen Massar Sent: zaterdag 25 juli 2009 23:45 To: Stream Service || Mark Scholten Cc: 'Per Heldal'; 'Nick Hilliard'; address-policy-wg at ripe.net Subject: Re: [address-policy-wg] Reopening discussion on RIPE Policy Proposal 2006-05 Stream Service || Mark Scholten wrote: > Hello Per, > > That would mean that ALL Ip addresses could be taken to another > provider/network and that it works. For example if a client has a /24 > PA and they go to another network they need the option to take it with them. This is why PI exists. Try using that as has been suggested already several times by other people. > At > least if you compare it to phone number portability in the Netherlands. If you are going to compare IP addresses to phone numbers, then you have to make the Internet work like the Phone system, which would basically mean a 'flow based' routing system: at connect time get the destination, store this and presto keep on using that. This does not work for the Internet as routes change (for phone you get a disconnect when a route changes due to a fiber cut or some other such event. For the Internet, where a sender could just start spewing packets to a million destinations, and possibly from a million sources, flow-based routing does not work, take a small guess why. Also, this is a POLICY list, not a TECHNICAL PROPOSAL list, for the latter there is the IRTF, note the R for Research, as the IETF is not even ready for these kind of changes (rrg WG comes in mind though). Greets, Jeroen
- Previous message (by thread): [address-policy-wg] Reopening discussion on RIPE Policy Proposal 2006-05
- Next message (by thread): [address-policy-wg] Reopening discussion on RIPE Policy Proposal 2006-05
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]