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/db-wg@ripe.net/
Proposal for adding external repository reference to import/expor t attributes
- Previous message (by thread): call for input: draft agenda DB-WG RIPE#43, Rhodes, GR
- Next message (by thread): Proposal for adding external repository reference to import/e xpor t attributes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mark Prior
mrp at mrp.net
Sat Aug 24 14:08:19 CEST 2002
At 3:10 PM -0400 23/8/02, Curtis Villamizar wrote: >It is possible to reactivate a WG on the mailing list only, for the >purpose of updating an existing RFC and not having a meeting. This >was done with TCPLW for RFC1323. Cengiz would need to update RPSL (as >primary author and keeper of the source of that document). > >Is the only change needed at this point the :: notation to indicate >external repository? If so, no change is needed to RFC-2622 since the >:: notation is called for in RFC-2725 and it wouldn't be worth >updating RFC-2622 just for that. > >What you really need to do is get Larry Blunk to update the ISI tools. Curtis, I wasn't the person suggesting making changes, I was just suggesting that you needed to follow a procedure in order to make it happen and couldn't just "fix" it in software. I would suggest if people think this is a good idea (and I haven't really thought about it) then perhaps merging it into the RPSLng work would be the way to go. Mark.
- Previous message (by thread): call for input: draft agenda DB-WG RIPE#43, Rhodes, GR
- Next message (by thread): Proposal for adding external repository reference to import/e xpor t attributes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]