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] Need for "import-via:" and "export-via:" attributes in AUT-NUM object
- Previous message (by thread): [routing-wg] Need for "import-via:" and "export-via:" attributes in AUT-NUM object
- Next message (by thread): [routing-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
Wed Nov 27 18:51:13 CET 2013
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, > Bullet point pitch: > > - The change is backwards compatible with older RPSL parsers. - The > new attributes are completely optional. - This change adds advanced > functionality that will especially benefit route server operators > and participants. 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). Job: What are the plans for advancing the I-D? 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/ iEYEARECAAYFAlKWMREACgkQF83fs8P8zalu1ACgwlCUB8Jc23I0LtvZR6cgW1m2 87oAn0omzasDIhWxX23uvwaBPSUel3OV =QExP -----END PGP SIGNATURE-----
- Previous message (by thread): [routing-wg] Need for "import-via:" and "export-via:" attributes in AUT-NUM object
- Next message (by thread): [routing-wg] Need for "import-via:" and "export-via:" attributes in AUT-NUM object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]