Cisco Systems OL-10984-01 Medical Alarms User Manual


 
This document and the information contained herein are provided on an"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE
DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Intellectual Property
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 IETF's procedures with respect
to rights in IETF 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.
AES
Copyright (C) Mok-Kong Shen 2003. mok-kong.shen@t-online.de
Free license:
This work and all modified versions of it may be freely copied, modified, redistributed and used for all legal civilian purposes without formality albeit
at licensee's own risk and responsibility, subject to the following conditions:
(1) A copy of this copyright notice with the release history list and the site modification history list must be included in any copy of this work or any
modified version of it.
(2) If this work or any modified version of it forms part of a software in object code or binary code, a document for users should accompany the
software stating this fact and include this copyright notice as well as an URL of the licensee where the source code of the package in the version
actually being used in the software can be found.
(3) Any modification (except dropping of the Supplement) should be appropriately documented in the site modification history list below. The last
date of site modification (at the beginning of the package) is to be updated.
(4) In case of non-trivial modifications, i.e. those stemming from efficiency or correctness considerations or from issues of interoperability with other
AES implementations, a copy of the modified package is to be immediately sent to the copyright owner at the address above.
(5) Eventual negative or unfavourable consequences and losses or damages of any form to any persons in connection with the use of this work or its
modified versions do not constitute any liabilities on the part of the copyright owner.
This free license is unlimited in time [1]. Any attempt of non-compliance with the above terms or any occurence of // their practical unsatisfiability
due to whatever reasons, however, automatically terminates the license. Such termination does not affect other licensees who have previously
obtained materials from the person with the terminated license but who continue to comply with the above terms.
Other licenses:
Any usages of the contents of the package that don't qualify for a free license as stated in the above require explicit // specific licenses from the
copyright owner.
[1] Since copyright grants could be revoked after 35 years (see http://www.copyright.gov/title17/92chap2.html#203), it // could be argued that this
license is not timeless for sure On the other hand, the lifespan of AES itself isn't likely to exceed that period. So the issue is not practically relevant
in our context.
DES - (http://www.itl.nist.gov/fipspubs/fip46-2.htm)