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

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    behave mailing list <behave@ietf.org>,
    behave chair <behave-chairs@tools.ietf.org>
Subject: Protocol Action: 'Common requirements for Carrier Grade NATs (CGNs)' to Best Current Practice (draft-ietf-behave-lsn-requirements-09.txt)

The IESG has approved the following document:
- 'Common requirements for Carrier Grade NATs (CGNs)'
  (draft-ietf-behave-lsn-requirements-09.txt) as Best Current Practice

This document is the product of the Behavior Engineering for Hindrance
Avoidance Working Group.

The IESG contact persons are Wesley Eddy and Martin Stiemerling.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-behave-lsn-requirements/

Ballot Text

Technical Summary

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


Working Group Summary

Consensus is strong, except for a split between some WG members wanting
"SHOULD support bulk port allocation" (in order to reduce logging) and
other WG members who think no recommendation should be made. So,
the document merely describes the trade-offs in its Section 5. 

An IPR declaration exists against the document,
https://datatracker.ietf.org/ipr/1648.  The actual claims are
not available.

At IETF82, consensus of the working group was to continue with
publication of the document. 


Document Quality

This is a requirements document, so there are not exactly
implementations of it.  Service providers are interested in it, and
vendors are interested in supporting these requirements for that
reason.


Personnel

The document shepherd is Dan Wing (dwing@cisco.com), and the
responsible AD is Wesley Eddy (wes@mti-systems.com).


RFC Editor Note

Please change the REQ-7 requirement as indicated below:

OLD:
   REQ-7:  It is RECOMMENDED that a CGN have an "Endpoint-Independent

NEW:
   REQ-7:  It is RECOMMENDED that a CGN use an "Endpoint-Independent

RFC Editor Note