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] BGP Update Report
- Next message (by thread): [routing-wg] [db-wg] Need for "import-via:" and "export-via:" attributes in AUT-NUM object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rob Evans
rhe at nosc.ja.net
Thu Dec 12 16:38:12 CET 2013
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi db-wg and routing-wg, > 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. There was mild support before RIPE 67, and the NCC have asked if we can now declare consensus and move on. My interpretation is "yes." Cheers, Rob -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKp2GQACgkQF83fs8P8zalp7wCfbMI6Cr1/kIZ+u1ZvTERaVjha BJkAn3x+GTjxrq9EE3AZvzPnlkt5ceJz =MEex -----END PGP SIGNATURE-----
- Previous message (by thread): [routing-wg] BGP Update Report
- Next message (by thread): [routing-wg] [db-wg] Need for "import-via:" and "export-via:" attributes in AUT-NUM object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]