[lacnog] Fwd: Fwd: I-D Action:draft-azinger-scalable-addressing-00.txt

[Fernando Gont]

Folks,

FYI.

-------- Original Message --------
Subject: Fwd: I-D Action:draft-azinger-scalable-addressing-00.txt
Date: Fri, 24 Sep 2010 23:51:05 -0700
From: Fred Baker <fred en cisco.com>
To: IPv6 operators forum <ipv6-ops en lists.cluenet.de>
CC: Paul Wilson <pwilson en apnic.net>, John Curran <jcurran en arin.net>,
    Axel Pawlik <axel en ripe.net>, Raul Echeberria <raul en lacnic.net>,
   "Adiel A.Akplogan" <ceo en afrinic.net>

I would appreciate opinions from the operators forum; please post
comments to v6ops en ietf.org.

The IPv6 Operations Working Group has been asked to adopt this document
as a working group draft. In essence, the outcome would become a
suggestion to the RIR and *NOG communities regarding the way the IETF
would suggest that IPv6 prefixes be allocated. Note the use of the word
"suggest". In summary, what this says is that the IETF holds no strong
opinions about specific prefix lengths or boundaries, but strongly feels
that the allocation policies should be scalable - which means that PI
allocations to edge networks should be done only when Really Truly
Appropriate.

My question is: is this something that the operational community would
consider helpful, or is it something the operational community would
prefer the IETF kept its nose out of? If the operational community would
find it helpful, is the specific suggestion reasonable from an
operational perspective?

Fred Baker
Chair IPv6 Operations WG

Begin forwarded message:

> From: Internet-Drafts en ietf.org
> Date: September 24, 2010 12:45:06 PM PDT
> To: i-d-announce en ietf.org
> Subject: I-D Action:draft-azinger-scalable-addressing-00.txt 
> Reply-To: internet-drafts en ietf.org
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 	Title           : A Scalable Addressing Allocation Architecture for IPv6
> 	Author(s)       : M. Azinger, et al.
> 	Filename        : draft-azinger-scalable-addressing-00.txt
> 	Pages           : 14
> 	Date            : 2010-09-24
> 
> This document presents a scalable architecture for assigning and
> aggregating IPv6 address space.  The current IPv4 addressing
> aggregation strategy was defined in [RFC1519] (and updated in
> [RFC4632]) and the IPv4 address allocation architecture was defined
> in [RFC1518].  A similar address allocation architecture was proposed
> for IPv6 in [RFC1887].  The objective of this document is to update
> the previous documents and provide the best current guidance on an
> address allocation architecture to help manage the growth of routing
> tables in IPv6.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-azinger-scalable-addressing-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.

------------ próxima parte ------------
A non-text attachment was scrubbed...
Name: no disponible
Type: text/plain<br>content-id: &lt
Size: 1 bytes
Desc: no disponible
URL: <https://mail.lacnic.net/pipermail/lacnog/attachments/20100925/ab0a966a/attachment.bin>
------------ próxima parte ------------
An embedded and charset-unspecified text was scrubbed...
Name: Attached Message Part
URL: <https://mail.lacnic.net/pipermail/lacnog/attachments/20100925/ab0a966a/attachment.ksh>