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

[Fred Baker]

I would appreciate opinions from the operators forum; please post comments to v6ops at 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 at ietf.org
> Date: September 24, 2010 12:45:06 PM PDT
> To: i-d-announce at ietf.org
> Subject: I-D Action:draft-azinger-scalable-addressing-00.txt 
> Reply-To: internet-drafts at 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/plain<br>content-id: &lt
Size: 0 bytes
Desc: not available
Url : http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20100924/dd3585ab/attachment.bin 
-------------- next part --------------
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce at 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