[Pppext] [Fwd: I-D ACTION:draft-fleischhauer-ipv4-addr-saving-00.txt]

James Carlson <carlsonj@workingcode.com> Tue, 08 March 2011 15:29 UTC

Message-ID: <4D764B99.7030501@workingcode.com>
Date: Tue, 08 Mar 2011 10:30:33 -0500
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
To: PPP Extensions <pppext@ietf.org>
Content-Type: multipart/mixed; boundary="------------030107080103080202030006"
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
Subject: [Pppext] [Fwd: I-D ACTION:draft-fleischhauer-ipv4-addr-saving-00.txt]
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2011 15:29:31 -0000

I see nothing particularly new here -- just a rehash of the existing
ability to negotiate NCPs when and where desired -- but since it
describes PPP mechanisms directly, I'm forwarding it along to the list.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

--- Begin Message ---

A new Internet-Draft is available from the on-line Internet-Drafts directories.

Title : On demand IPv4 address provisioning in Dual-Stack PPP deployment scenarios
Author(s) : O. Bonness, et al
Filename : draft-fleischhauer-ipv4-addr-saving-00.txt
Pages : 10
Date : 2011-03-07

Today the Dual-Stack approach is the most straightforward and most
common way for introducing IPv6 into existing systems and networks.
However a typical drawback of implementing Dual-Stack is that each
node will still require at least one IPv4 address. Hence, solely
deploying Dual-Stack does not provide a sufficient solution to the
IPv4 address exhaustion problem. Assuming a situation where most of
the IP communication (e.g. always-on, VoIP etc.) can be provided via
IPv6, the usage of IPv4 addresses can significantly be reduced and
the unused IPv4 addresses can under certain circumstances be returned
to the IPv4 address pool of the service provider. New Dual-Stack
enabled services can be introduced without increasing the IPv4
address demand, when IPv6 will be the preferred network layer
protocol. This document describes such a solution in a Dual-Stack
PPP session network scenario and explains the protocol mechanisms
which are used.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-fleischhauer-ipv4-addr-saving-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

ftp://ftp.ietf.org/internet-drafts/draft-fleischhauer-ipv4-addr-saving-00.txt"><ftp://ftp.ietf.org/internet-drafts/draft-fleischhauer-ipv4-addr-saving-00.txt>

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--- End Message ---

[Pppext] [Fwd: I-D ACTION:draft-fleischhauer-ipv4… James Carlson