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

The information below is for an old version of the document
Document Type Active Internet-Draft (behave WG)
Last updated 2012-03-29 (latest revision 2011-11-30)
Replaces draft-nishitani-cgn
Stream IETF
Intended RFC status Best Current Practice
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state AD Evaluation::Revised I-D Needed
Telechat date
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
Intended status: BCP                                         I. Yamagata
Expires: June 2, 2012                                        S. Miyakawa
                                                      NTT Communications
                                                             A. Nakagawa
                                          Japan Internet Exchange (JPIX)
                                                               H. Ashida
                                                      IS Consulting G.K.
                                                       November 30, 2011

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

Abstract

   This document defines common requirements for Carrier-Grade NAT
   (CGN).

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on June 2, 2012.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Perreault, et al.         Expires June 2, 2012                  [Page 1]
Internet-Draft              CGN Requirements               November 2011

   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
   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 BSD License.

Table of Contents

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

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

1.  Introduction

   With the shortage of IPv4 addresses, it is expected that more 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 NAT 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.

   This is not to be considered a solution to the shortage of IPv4
Show full document text