Common requirements for Carrier Grade NATs (CGNs)
draft-ietf-behave-lsn-requirements-07

The information below is for an old version of the document
Document Type Active Internet-Draft (behave WG)
Last updated 2012-07-10 (latest revision 2012-06-13)
Replaces draft-nishitani-cgn
Stream IETF
Intended RFC status Best Current Practice
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation
Telechat date
Needs a YES. Needs 5 more YES or NO OBJECTION positions to pass.
Responsible AD Wesley Eddy
IESG note Dan Wing (dwing@cisco.com) is the document shepherd.
Send notices to behave-chairs@tools.ietf.org, draft-ietf-behave-lsn-requirements@tools.ietf.org
Internet Engineering Task Force                        S. Perreault, Ed.
Internet-Draft                                                  Viagenie
Updates: 4787 (if approved)                                  I. Yamagata
Intended status: BCP                                         S. Miyakawa
Expires: December 15, 2012                            NTT Communications
                                                             A. Nakagawa
                                          Japan Internet Exchange (JPIX)
                                                               H. Ashida
                                                      IS Consulting G.K.
                                                           June 13, 2012

           Common requirements for Carrier Grade NATs (CGNs)
                 draft-ietf-behave-lsn-requirements-07

Abstract

   This document defines common requirements for Carrier-Grade NAT
   (CGN).  It updates RFC 4787.

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 December 15, 2012.

Copyright Notice

   Copyright (c) 2012 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
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

Perreault, et al.       Expires December 15, 2012               [Page 1]
Internet-Draft              CGN Requirements                   June 2012

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Requirements for CGNs  . . . . . . . . . . . . . . . . . . . .  5
   4.  Logging  . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
   5.  Bulk Port Allocation . . . . . . . . . . . . . . . . . . . . . 11
   6.  Deployment Considerations  . . . . . . . . . . . . . . . . . . 12
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 12
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     10.1.  Normative References  . . . . . . . . . . . . . . . . . . 13
     10.2.  Informative Reference . . . . . . . . . . . . . . . . . . 14
   Appendix A.  Change Log (to be removed by RFC Editor prior to
                publication)  . . . . . . . . . . . . . . . . . . . . 15
     A.1.   Changed in -07  . . . . . . . . . . . . . . . . . . . . . 15
     A.2.   Changed in -06  . . . . . . . . . . . . . . . . . . . . . 16
     A.3.   Changed in -05  . . . . . . . . . . . . . . . . . . . . . 17
     A.4.   Changed in -04  . . . . . . . . . . . . . . . . . . . . . 17
     A.5.   Changed in -03  . . . . . . . . . . . . . . . . . . . . . 17
     A.6.   Changed in -02  . . . . . . . . . . . . . . . . . . . . . 18
     A.7.   Changed in -01  . . . . . . . . . . . . . . . . . . . . . 19
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19

Perreault, et al.       Expires December 15, 2012               [Page 2]
Internet-Draft              CGN Requirements                   June 2012

1.  Introduction

   With the shortage of IPv4 addresses, it is expected that more
   Internet Service Providers (ISPs) may want to provide a service where
   a public IPv4 address would be shared by many subscribers.  Each
   subscriber is assigned a private address, and a Network Address
   Translator (NAT) [RFC2663] situated in the ISP's network translates
   between private and public addresses.  When a second IPv4 NAT is
   located at the customer edge, this results in two layers of NAT.
Show full document text