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/routing-wg@ripe.net/
[routing-wg] [db-wg] Need for "import-via:" and "export-via:" attributes in AUT-NUM object
- Previous message (by thread): [routing-wg] [db-wg] Need for "import-via:" and "export-via:" attributes in AUT-NUM object
- Next message (by thread): [routing-wg] May a tier1 transit change bgp origin attribute?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Piotr Strzyzewski
Piotr.Strzyzewski at polsl.pl
Thu Dec 12 22:18:48 CET 2013
On Thu, Dec 12, 2013 at 03:38:12PM +0000, Rob Evans wrote: > > Can I encourage those that have an opinion about this to voice it? > > The NCC would like some confirmation from the community that there > > is some demand to implement this (and no objection to doing it). > > The only feedback since that message has been from Nick who, if I may > summarise, said that he didn't object, it may serve some use, but this > creates an ugly (but inevitable) fork in RPSL. If this change anything: I do not object. :) Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski at polsl.pl
- Previous message (by thread): [routing-wg] [db-wg] Need for "import-via:" and "export-via:" attributes in AUT-NUM object
- Next message (by thread): [routing-wg] May a tier1 transit change bgp origin attribute?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]