On 5/23/18 10:16 AM, Warren Kumari wrote: > > > On Wed, May 23, 2018 at 1:09 PM Nick Hilliard <[email protected] > <mailto:[email protected]>> wrote: > > This errata report isn't wrong, but belongs to a bigger category of > problems relating to how the IETF handles third party references > in RFCs. > > It's unlikely that the researchgate url will be persistent in the > longer > term, at least any more than any other URL. > > > I marked it as Hold for Document Update -- this seems to be the > "best" way to annotate documents with things like this. > More generally the citation accurately describes the paper. At some point in the future when we are long dead, it will still be a reference to the paper.
Assuming that there is a method by which we can stably maintain references to documents through URLs over the course of decades is misguided. > Thanks! > W > > > > > Nick > > RFC Errata System wrote: > > The following errata report has been submitted for RFC7948, > > "Internet Exchange BGP Route Server Operations". > > > > -------------------------------------- > > You may review the report below and at: > > http://www.rfc-editor.org/errata/eid5366 > > > > -------------------------------------- > > Type: Technical > > Reported by: Greg Skinner <[email protected] > <mailto:[email protected]>> > > > > Section: 6.2 > > > > Original Text > > ------------- > > [RS-ARCH] Govindan, R., Alaettinoglu, C., Varadhan, K., and D. > > Estrin, "A Route Server Architecture for Inter-Domain > > Routing", 1995, > > <http://www.cs.usc.edu/assets/003/83191.pdf>. > > > > Corrected Text > > -------------- > > [RS-ARCH] Govindan, R., Alaettinoglu, C., Varadhan, K., and D. > > Estrin, "A Route Server Architecture for Inter-Domain > > Routing", 1995, > > <https://www.researchgate.net/ > > publication/ > > 2297181_A_Route_Server_Architecture_for_Inter-Domain_Routing> > > > > Notes > > ----- > > The paper is no longer accessible from the www.cs.usc.edu > <http://www.cs.usc.edu> site. A related paper can be accessed at > https://doi.org/10.1016/S0169-7552(98)00008-7 > <https://doi.org/10.1016/S0169-7552%2898%2900008-7> by those who > are registered members or will pay for the paper. It would be > cited as: > > [RS-ARCH] Govindan, R., Alaettinoglu, C., Varadhan, K., and D. > > Estrin, "A Route Server Architecture for > Inter-Domain > > Routing", Computer Networks and ISDN Systems, > Volume 30, > > Issue 12, 13 July 1998, Pages 1157-1174, > > > <https://doi.org/10.1016/S0169-7552(98)00008-7 > <https://doi.org/10.1016/S0169-7552%2898%2900008-7>>. > > > > Sorry, I had to split the link in the corrected text to satisfy > the 72-character line length requirement in the corrected text. > > > > Instructions: > > ------------- > > This erratum is currently posted as "Reported". If necessary, please > > use "Reply All" to discuss whether it should be verified or > > rejected. When a decision is reached, the verifying party > > can log in to change the status and edit the report, if necessary. > > > > -------------------------------------- > > RFC7948 (draft-ietf-grow-ix-bgp-route-server-operations-05) > > -------------------------------------- > > Title : Internet Exchange BGP Route Server Operations > > Publication Date : September 2016 > > Author(s) : N. Hilliard, E. Jasinska, R. Raszuk, N. Bakker > > Category : INFORMATIONAL > > Source : Global Routing Operations > > Area : Operations and Management > > Stream : IETF > > Verifying Party : IESG > > > > _______________________________________________ > > GROW mailing list > > [email protected] <mailto:[email protected]> > > https://www.ietf.org/mailman/listinfo/grow > > > > > > -- > I don't think the execution is relevant when it was obviously a bad > idea in the first place. > This is like putting rabid weasels in your pants, and later expressing > regret at having chosen those particular rabid weasels and that pair > of pants. > ---maf > > > _______________________________________________ > GROW mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/grow
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
