< draft-bng-radext-virtual-nas-for-dnas-00.txt   draft-bng-radext-virtual-nas-for-dnas-01.txt >
Network Working Group RaghunadhaReddy. Pocha, Ed. Network Working Group RaghunadhaReddy. Pocha, Ed.
Internet-Draft ChandraShekar. Jamadarkhani, Ed. Internet-Draft ChandraShekar. Jamadarkhani, Ed.
Intended status: Standards Track Satyanarayana. Danda Intended status: Standards Track Satyanarayana. Danda
Expires: December 8, 2017 Nishad. M Expires: June 8, 2018 Nishad. M
Nagappa. Chinnannavar Nagappa. Chinnannavar
Cisco Systems Cisco Systems
June 6, 2017 December 5, 2017
Virtual NAS (vNAS) Support for DNAS Virtual NAS (vNAS) Support for DNAS
draft-bng-radext-virtual-nas-for-dnas-00 draft-bng-radext-virtual-nas-for-dnas-01
Abstract Abstract
This specification defines a framework for interacting North bound This specification defines a framework for interacting North bound
(AAA/Policy) servers of the Client resides in Cloud and/or (AAA/Policy) servers of the Client resides in Cloud and/or
Distributed Network environment with High-Availability to achieve Distributed Network environment with High-Availability to achieve
fewer use-cases. First, NAS Client resides in Cloud or Virtualized fewer use-cases. First, NAS Client resides in Cloud or Virtualized
or Distributed Network Access System to perform Authorization, or Distributed Network Access System to perform Authorization,
Authentication and Accounting procedures with AAA Servers. Second, Authentication and Accounting procedures with AAA Servers. Second,
AAAA/Policy Servers provide dynamic policy information for AAAA/Policy Servers provide dynamic policy information for
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Available conditions. Available conditions.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on December 8, 2017. This Internet-Draft will expire on June 8, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
skipping to change at page 15, line 43 skipping to change at page 15, line 43
center networks, it does not itself introduce any security risks. center networks, it does not itself introduce any security risks.
However, it is clear that security concerns need to be a However, it is clear that security concerns need to be a
consideration of any solutions proposed to address this problem consideration of any solutions proposed to address this problem
space. Solutions will need to address both data-plane and control- space. Solutions will need to address both data-plane and control-
plane security concerns. plane security concerns.
10. Informative References 10. Informative References
[RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, [RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321,
DOI 10.17487/RFC1321, April 1992, DOI 10.17487/RFC1321, April 1992,
<http://www.rfc-editor.org/info/rfc1321>. <https://www.rfc-editor.org/info/rfc1321>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC2234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, DOI 10.17487/RFC2234, Specifications: ABNF", RFC 2234, DOI 10.17487/RFC2234,
November 1997, <http://www.rfc-editor.org/info/rfc2234>. November 1997, <https://www.rfc-editor.org/info/rfc2234>.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", "Remote Authentication Dial In User Service (RADIUS)",
RFC 2865, DOI 10.17487/RFC2865, June 2000, RFC 2865, DOI 10.17487/RFC2865, June 2000,
<http://www.rfc-editor.org/info/rfc2865>. <https://www.rfc-editor.org/info/rfc2865>.
[RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, [RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866,
DOI 10.17487/RFC2866, June 2000, DOI 10.17487/RFC2866, June 2000,
<http://www.rfc-editor.org/info/rfc2866>. <https://www.rfc-editor.org/info/rfc2866>.
[RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS [RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS
Extensions", RFC 2869, DOI 10.17487/RFC2869, June 2000, Extensions", RFC 2869, DOI 10.17487/RFC2869, June 2000,
<http://www.rfc-editor.org/info/rfc2869>. <https://www.rfc-editor.org/info/rfc2869>.
[RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", [RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6",
RFC 3162, DOI 10.17487/RFC3162, August 2001, RFC 3162, DOI 10.17487/RFC3162, August 2001,
<http://www.rfc-editor.org/info/rfc3162>. <https://www.rfc-editor.org/info/rfc3162>.
[RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote [RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote
Authentication Dial In User Service)", RFC 3575, Authentication Dial In User Service)", RFC 3575,
DOI 10.17487/RFC3575, July 2003, DOI 10.17487/RFC3575, July 2003,
<http://www.rfc-editor.org/info/rfc3575>. <https://www.rfc-editor.org/info/rfc3575>.
[RFC5176] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B. [RFC5176] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B.
Aboba, "Dynamic Authorization Extensions to Remote Aboba, "Dynamic Authorization Extensions to Remote
Authentication Dial In User Service (RADIUS)", RFC 5176, Authentication Dial In User Service (RADIUS)", RFC 5176,
DOI 10.17487/RFC5176, January 2008, DOI 10.17487/RFC5176, January 2008,
<http://www.rfc-editor.org/info/rfc5176>. <https://www.rfc-editor.org/info/rfc5176>.
Authors' Addresses Authors' Addresses
Raghunadha Reddy Pocha (editor) Raghunadha Reddy Pocha (editor)
Cisco Systems Cisco Systems
Cessna Business Park, Kadubeesanahalli Cessna Business Park, Kadubeesanahalli
Bengaluru 560103 Bengaluru 560103
India India
Phone: +91 9731 203 806 Phone: +91 9731 203 806
 End of changes. 15 change blocks. 
15 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/