rfc2865[1] (1027731), страница 14
Текст из файла (страница 14)
Литература[1] Rigney, C., Rubens, A., Simpson, W. and S. Willens, "Remote Authentication Dial In User Service (RADIUS)", RFC 2138, April 1997.[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 211921, March, 1997.[3] Rivest, R. and S. Dusse, "The MD5 Message-Digest Algorithm", RFC 132121, April 1992.[4] Postel, J., "User Datagram Protocol", STD 6, RFC 76821, August 1980.[5] Rigney, C., "RADIUS Accounting", RFC 286621, June 2000.[6] Reynolds, J. and J.
Postel, "Assigned Numbers", STD 2, RFC 1700 22, October 1994.[7] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC 2279, January 1998.[8] Aboba, B. and M. Beadles, "The Network Access Identifier", RFC 248621, January 1999.[9] Kaufman, C., Perlman, R., and Speciner, M., "Network Security: Private Communications in a Public World", Prentice Hall, March1995, ISBN 0-13-061466-1.[10] Jacobson, V., "Compressing TCP/IP headers for low-speed serial links", RFC 1144, February 1990.[11] ISO 8859.
International Standard -- Information Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 1: LatinAlphabet No. 1, ISO 8859-1:1987.[12] Sklower, K., Lloyd, B., McGregor, G., Carr, D. and T. Coradetti, "The PPP Multilink Protocol (MP)", RFC 1990, August 1996.[13] Alvestrand, H. and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.[14] Galvin, J., McCloghrie, K. and J. Davin, "SNMP Security Protocols", RFC 1352, July 1992.[15] Dobbertin, H., "The Status of MD5 After a Recent Attack", CryptoBytes Vol.2 No.2, Summer 1996.11. ПодтверждениеИсходный вариант протокола RADIUS был разработан Стивом Вилленсом (Steve Willens) из Livingston Enterprises для линейкисерверов доступа PortMaster.12.
Адрес руководителя группыВзаимодействием участников рабочей группы руководил:Carl RigneyLivingston Enterprises4464 Willow RoadPleasanton, California 94588Phone: +1 925 737 2100EMail: cdr@telemancy.com13. Адреса авторовСвязанные с этим документом вопросы можно адресовать авторам:Carl RigneyLivingston Enterprises4464 Willow RoadPleasanton, California 94588Phone: +1 925 737 2100EMail: cdr@telemancy.comAllan C. RubensMerit Network, Inc.4251 Plymouth RoadAnn Arbor, Michigan 48105-2785EMail: acr@merit.eduWilliam Allen SimpsonDaydreamer21Перевод документа на русский язык вы найдете на сайте www.protocols.ru.
Прим. перев.В соответствии с RFC 3232 документ STD 2 утратил силу. Значения Assigned Numbers следует искать в базе данных, доступнойна сайте www.iana.org/numbers.html. Прим. перев.www.bilim.com31www.protocols.ru22Разумные сети от компании BiLiM SystemsComputer Systems Consulting ServicesПеревод RFC 28651384 FontaineMadison Heights, Michigan 48071EMail: wsimpson@greendragon.comSteve WillensLivingston Enterprises4464 Willow RoadPleasanton, California 94588EMail: steve@livingston.comПеревод на русский языкНиколай Малыхnmalykh@bilim.com14.
Полное заявление авторских правCopyright (C) The Internet Society (2000). All Rights Reserved.This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it orassist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, providedthat the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself maynot be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations,except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the InternetStandards process must be followed, or as required to translate it into languages other than English.The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THEINTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOTLIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANYIMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.ПодтверждениеФинансирование функций RFC Editor обеспечивалось Internet Society.www.bilim.com32www.protocols.ru.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
