--- 1/draft-ietf-dime-nat-control-04.txt 2010-10-22 03:16:05.000000000 +0200 +++ 2/draft-ietf-dime-nat-control-05.txt 2010-10-22 03:16:05.000000000 +0200 @@ -1,63 +1,62 @@ Internet Engineering Task Force F. Brockners Internet-Draft S. Bhandari Intended status: Standards Track Cisco -Expires: April 19, 2011 V. Singh +Expires: April 25, 2011 V. Singh Mavenir Systems V. Fajardo Telcordia Technologies - October 16, 2010 + October 22, 2010 Diameter Network Address and Port Translation Control Application - draft-ietf-dime-nat-control-04 + draft-ietf-dime-nat-control-05 Abstract This document describes the framework, messages, and procedures for the Diameter Network address and port translation Control Application. This Diameter application allows per endpoint control - of large scale Network Address Translators and Network Address and - Port Translators, which are added to cope with IPv4-address space + of Network Address Translators and Network Address and Port + Translators, which are added to cope with IPv4-address space completion. This Diameter application allows external devices to configure and manage a Network Address Translator device - expanding the existing Diameter-based AAA and policy control capabilities with a Network Address Translators and Network Address and Port Translators control component. These external devices can be network elements in the data plane such as a Network Access Server, or can be more centralized control plane devices such as AAA-servers. This Diameter application establishes a context to commonly identify and - manage endpoints on a gateway or server, and a large scale Network - Address Translator and Network Address and Port Translator device. - This includes, for example, the control of the total number of - Network Address Translator bindings allowed or the allocation of a - specific Network Address Translator binding for a particular - endpoint. In addition, it allows large scale Network Address - Translator devices to provide information relevant to accounting - purposes. + manage endpoints on a gateway or server, and a Network Address + Translator and Network Address and Port Translator device. This + includes, for example, the control of the total number of Network + Address Translator bindings allowed or the allocation of a specific + Network Address Translator binding for a particular endpoint. In + addition, it allows Network Address Translator devices to provide + information relevant to accounting purposes. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on April 19, 2011. + This Internet-Draft will expire on April 25, 2011. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -1735,21 +1734,25 @@ a. Editorial changes suggested in WG Lastcall review b. Removed NCR Request type terminate and replaced with STR c. All references to Auth-Session-State are removed and a new section to describe FSM for Manager and Agent has been added d. Clarified reuse of External address and address pools among multiple subscribers + Changes from -04 to -05 + a. Removed references to Large Scale NAT as per review comments + 15. References + 15.1. Normative References [ETSIES283034] ETSI, "Telecommunications and Internet Converged Services and Protocols for Advanced Networks (TISPAN),Network Attachment Sub-System (NASS),e4 interface based on the Diameter protocol.", September 2008. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. @@ -1767,26 +1770,20 @@ February 2010. 15.2. Informative References [I-D.ietf-dime-diameter-qos] Sun, D., McCann, P., Tschofenig, H., ZOU), T., Doria, A., and G. Zorn, "Diameter Quality of Service Application", draft-ietf-dime-diameter-qos-14 (work in progress), February 2010. - [I-D.nishitani-cgn] - Nishitani, T., Yamagata, I., Miyakawa, S., Nakagawa, A., - and H. Ashida, "Common Functions of Large Scale NAT - (LSN)", draft-nishitani-cgn-03 (work in progress), - November 2009. - [RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter Network Access Server Application", RFC 4005, August 2005. [TS32299] "3rd Generation Partnership Project; Technical Specification Group Service and System Aspects; Telecommunication management; Charging management; "Diameter charging applications", 3GPP TS 32.299 Version 6.3.0.2", 2008.