Hi everyone, This is just a reminder that this is the last day to send in your additional requirements, for those of you not happy with Maldwyn's basic list was last Friday. (If anyone is really desparate to comment, we can extend it, but I get the impression that nobody is). Today, we begin the writing an initial version of the technical specs. Please email in with your speciication suggestions. Maldwyn and I both look forward to commenting. For the moment, let me suggest that the language of Choice should be Perl 5.6 or greater for the backend. I also believe that with regard to a GUI, the web would be the logical bridge between you Windows and you UNIX people. I am thinking that where possible, multi-browser JavaScript should be used to reduced server-side work. I think tha an adaptation of the IP libraries made available by Manuel should be used. Comments? ATB, Guy -- Guy Vegoda \ guy@vegoda.org *Please do not send html* NIC: GUY-RIPE \ guy@cryptography.org.uk *attachments* Unix, Linux Hobbyist \ +44(0)20 7961 8318 (work) www.thenakedfrenchman.com \ +44(0)958 469 532 (cell)
Hi everyone,
This is just a reminder that this is the last day to send in your additional requirements, for those of you not happy with Maldwyn's basic list was last Friday.
Not sure if these are useful or not, but consider, but some resources in which I discussed address management requirements: http://www.nanog.org/mtg-9811/ppt/berk/index.htm http://www.arin.net/minutes/ARIN199910/index.htm The latter presentation complemented Richard Jimmerson's presentation on the templates proper: http://www.arin.net/minutes/tutorial/index.htm While some of the tools described certainly do not deal with the LIR to RIR relationship, they do apply to the LIR to the LIR's customer. Also in managing the customer relationship, see the router renumbering guide, http://www.isi.edu/in-notes/rfc2072.txt
participants (2)
-
Guy Vegoda -
Howard C. Berkowitz