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]/
[routing-wg]Routing Aggregation Policy
- Previous message (by thread): [routing-wg]Routing Aggregation Policy
- Next message (by thread): [routing-wg]Routing Aggregation Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mike Hughes
mike at linx.net
Wed Oct 12 16:36:49 CEST 2005
--On 12 October 2005 06:41 -0700 "Barry Greene (bgreene)" <bgreene at cisco.com> wrote: > How would you enforce a policy like this (Other than peer pressure)? Okay, judging from some of the messages I've had privately, as well as this one, I obviously didn't make myself clear. As an enforceable policy this FAILED. The LINX members voted to reject any sort of interference in/policing of their routing, for a number of reasons. Once it had failed, I was given an action by the LINX General Meeting to take the bones of failed policy, as it stood at the time of the rejection, and offer it to the RIPE routing-wg as the basis for a Best Practice document, which by nature is non-enforceable. Cheers, Mike -- Mike Hughes Chief Technical Officer London Internet Exchange mike at linx.net http://www.linx.net/ "Only one thing in life is certain: init is Process #1"
- Previous message (by thread): [routing-wg]Routing Aggregation Policy
- Next message (by thread): [routing-wg]Routing Aggregation Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]