Diameter RFC3588

download Diameter RFC3588

of 74

Transcript of Diameter RFC3588

  • 8/3/2019 Diameter RFC3588

    1/74

  • 8/3/2019 Diameter RFC3588

    2/74

  • 8/3/2019 Diameter RFC3588

    3/74

  • 8/3/2019 Diameter RFC3588

    4/74

  • 8/3/2019 Diameter RFC3588

    5/74

  • 8/3/2019 Diameter RFC3588

    6/74

  • 8/3/2019 Diameter RFC3588

    7/74

  • 8/3/2019 Diameter RFC3588

    8/74

  • 8/3/2019 Diameter RFC3588

    9/74

  • 8/3/2019 Diameter RFC3588

    10/74

  • 8/3/2019 Diameter RFC3588

    11/74

  • 8/3/2019 Diameter RFC3588

    12/74

  • 8/3/2019 Diameter RFC3588

    13/74

  • 8/3/2019 Diameter RFC3588

    14/74

  • 8/3/2019 Diameter RFC3588

    15/74

  • 8/3/2019 Diameter RFC3588

    16/74

  • 8/3/2019 Diameter RFC3588

    17/74

  • 8/3/2019 Diameter RFC3588

    18/74

  • 8/3/2019 Diameter RFC3588

    19/74

  • 8/3/2019 Diameter RFC3588

    20/74

  • 8/3/2019 Diameter RFC3588

    21/74

  • 8/3/2019 Diameter RFC3588

    22/74

  • 8/3/2019 Diameter RFC3588

    23/74

  • 8/3/2019 Diameter RFC3588

    24/74

  • 8/3/2019 Diameter RFC3588

    25/74

  • 8/3/2019 Diameter RFC3588

    26/74

  • 8/3/2019 Diameter RFC3588

    27/74

  • 8/3/2019 Diameter RFC3588

    28/74

  • 8/3/2019 Diameter RFC3588

    29/74

  • 8/3/2019 Diameter RFC3588

    30/74

  • 8/3/2019 Diameter RFC3588

    31/74

  • 8/3/2019 Diameter RFC3588

    32/74

  • 8/3/2019 Diameter RFC3588

    33/74

  • 8/3/2019 Diameter RFC3588

    34/74

  • 8/3/2019 Diameter RFC3588

    35/74

  • 8/3/2019 Diameter RFC3588

    36/74

  • 8/3/2019 Diameter RFC3588

    37/74

  • 8/3/2019 Diameter RFC3588

    38/74

  • 8/3/2019 Diameter RFC3588

    39/74

  • 8/3/2019 Diameter RFC3588

    40/74

  • 8/3/2019 Diameter RFC3588

    41/74

  • 8/3/2019 Diameter RFC3588

    42/74

  • 8/3/2019 Diameter RFC3588

    43/74

  • 8/3/2019 Diameter RFC3588

    44/74

  • 8/3/2019 Diameter RFC3588

    45/74

  • 8/3/2019 Diameter RFC3588

    46/74

  • 8/3/2019 Diameter RFC3588

    47/74

  • 8/3/2019 Diameter RFC3588

    48/74

  • 8/3/2019 Diameter RFC3588

    49/74

  • 8/3/2019 Diameter RFC3588

    50/74

  • 8/3/2019 Diameter RFC3588

    51/74

  • 8/3/2019 Diameter RFC3588

    52/74

  • 8/3/2019 Diameter RFC3588

    53/74

  • 8/3/2019 Diameter RFC3588

    54/74

  • 8/3/2019 Diameter RFC3588

    55/74

  • 8/3/2019 Diameter RFC3588

    56/74

  • 8/3/2019 Diameter RFC3588

    57/74

  • 8/3/2019 Diameter RFC3588

    58/74

  • 8/3/2019 Diameter RFC3588

    59/74

  • 8/3/2019 Diameter RFC3588

    60/74

  • 8/3/2019 Diameter RFC3588

    61/74

  • 8/3/2019 Diameter RFC3588

    62/74

  • 8/3/2019 Diameter RFC3588

    63/74

  • 8/3/2019 Diameter RFC3588

    64/74

  • 8/3/2019 Diameter RFC3588

    65/74

  • 8/3/2019 Diameter RFC3588

    66/74

  • 8/3/2019 Diameter RFC3588

    67/74

  • 8/3/2019 Diameter RFC3588

    68/74

  • 8/3/2019 Diameter RFC3588

    69/74

  • 8/3/2019 Diameter RFC3588

    70/74

  • 8/3/2019 Diameter RFC3588

    71/74

  • 8/3/2019 Diameter RFC3588

    72/74

    RFC 3588 Diameter Based Protocol September 2003

    Appendix D. Intellectual Property Statement

    The IETF takes no position regarding the validity or scope of any

    intellectual property or other rights that might be claimed to

    RFC 3588 Diameter Based Protocol September 2003

    Authors' Addresses

    Pat R. Calhoun

    Airespace, Inc.

  • 8/3/2019 Diameter RFC3588

    73/74

    te ectua p ope ty o ot e g ts t at g t be c a ed to

    pertain to the implementation or use of the technology described in

    this document or the extent to which any license under such rightsmight or might not be available; neither does it represent that it

    has made any effort to identify any such rights. Information on the

    IETF's procedures with respect to rights in standards-track andstandards-related documentation can be found in BCP-11. Copies of

    claims of rights made available for publication and any assurances of

    licenses to be made available, or the result of an attempt made toobtain 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 Secretariat.

    The IETF invites any interested party to bring to its attention any

    copyrights, patents or patent applications, or other proprietaryrights which may cover technology that may be required to practice

    this standard. Please address the information to the IETF Executive

    Director.

    Calhoun, et al. Standards Track [Page 145]

    espace, c.

    110 Nortech Parkway

    San Jose, California, 95134USA

    Phone: +1 408-635-2023Fax: +1 408-635-2020

    EMail: [email protected]

    John Loughney

    Nokia Research Center

    Itamerenkatu 11-1300180 Helsinki

    Finland

    Phone: +358 50 483 6242

    EMail: [email protected]

    Jari Arkko

    Ericsson

    02420 JorvasFinland

    Phone: +358 40 5079256EMail: [email protected]

    Erik Guttman

    Sun Microsystems, Inc.Eichhoelzelstr. 7

    74915 Waibstadt

    Germany

    Phone: +49 7263 911 701

    EMail: [email protected]

    Glen Zorn

    Cisco Systems, Inc.

    500 108th Avenue N.E., Suite 500Bellevue, WA 98004

    USA

    Phone: +1 425 438 8218

    Calhoun, et al. Standards Track [Page 146]

    RFC 3588 Diameter Based Protocol September 2003

    Full Copyright Statement

    Copyright (C) The Internet Society (2003). All Rights Reserved.

  • 8/3/2019 Diameter RFC3588

    74/74

    This document and translations of it may be copied and furnished to

    others, and derivative works that comment on or otherwise explain itor assist in its implementation may be prepared, copied, published

    and distributed, in whole or in part, without restriction of any

    kind, provided that the above copyright notice and this paragraph areincluded on all such copies and derivative works. However, this

    document itself may not be modified in any way, such as by removing

    the copyright notice or references to the Internet Society or otherInternet organizations, except as needed for the purpose of

    developing Internet standards in which case the procedures for

    copyrights defined in the Internet Standards process must befollowed, 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 THE INTERNET ENGINEERING

    TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDINGBUT 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.

    Acknowledgement

    Funding for the RFC Editor function is currently provided by the

    Internet Society.

    Calhoun, et al. Standards Track [Page 147]