draft-ietf-krb-wg-rfc1510ter-00.txt   draft-ietf-krb-wg-rfc1510ter-01.txt 
INTERNET-DRAFT Tom Yu INTERNET-DRAFT Tom Yu
draft-ietf-krb-wg-rfc1510ter-00.txt MIT draft-ietf-krb-wg-rfc1510ter-01.txt MIT
Expires: 25 July 2005 21 January 2005 Expires: 19 March 2005 15 September 2005
The Kerberos Network Authentication Service (Version 5) The Kerberos Network Authentication Service (Version 5)
Status of This Memo Status of This Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, applicable patent or other IPR claims of which he or she is aware
or will be disclosed, and any of which I become aware will be have been or will be disclosed, and any of which he or she becomes
disclosed, in accordance with RFC 3668. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
skipping to change at page 4, line 32 skipping to change at page 4, line 32
13. IANA Considerations ......................................... 68 13. IANA Considerations ......................................... 68
14. Acknowledgments ............................................. 69 14. Acknowledgments ............................................. 69
Appendices ....................................................... 69 Appendices ....................................................... 69
A. ASN.1 Module (Normative) ..................................... 69 A. ASN.1 Module (Normative) ..................................... 69
B. Kerberos and Character Encodings (Informative) ...............103 B. Kerberos and Character Encodings (Informative) ...............103
C. Kerberos History (Informative) ...............................104 C. Kerberos History (Informative) ...............................104
D. Notational Differences from [KCLAR] ..........................105 D. Notational Differences from [KCLAR] ..........................105
Normative References .............................................106 Normative References .............................................106
Informative References ...........................................106 Informative References ...........................................106
Author's Address .................................................108 Author's Address .................................................108
Full Copyright Statement .........................................108 Copyright Statement ..............................................108
Intellectual Property Statement ..................................108
1. Introduction 1. Introduction
The Kerberos network authentication protocol is a trusted-third-party The Kerberos network authentication protocol is a trusted-third-party
protocol utilizing symmetric-key cryptography. It assumes that all protocol utilizing symmetric-key cryptography. It assumes that all
communications between parties in the protocol may be arbitrarily communications between parties in the protocol may be arbitrarily
tampered with or monitored, and that the security of the overall tampered with or monitored, and that the security of the overall
system depends only on the effectiveness of the cryptographic system depends only on the effectiveness of the cryptographic
techniques and the secrecy of the cryptographic keys used. The techniques and the secrecy of the cryptographic keys used. The
Kerberos protocol authenticates an application client's identity to Kerberos protocol authenticates an application client's identity to
skipping to change at page 108, line 19 skipping to change at page 108, line 19
X.690 (2002) | ISO/IEC 8825-1:2002. X.690 (2002) | ISO/IEC 8825-1:2002.
Author's Address Author's Address
Tom Yu Tom Yu
77 Massachusetts Ave 77 Massachusetts Ave
Cambridge, MA 02139 Cambridge, MA 02139
USA USA
tlyu@mit.edu tlyu@mit.edu
Full Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
 End of changes. 6 change blocks. 
9 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.28, available from http://www.levkowetz.com/ietf/tools/rfcdiff/