Hi Thomas,

I've read yesterday this document, and I'm basically ok with it, but with
two considerations that I think must be worked out it parallel somehow:
1) HD-Ratio modification, as it seems to be an integral part of the
discussion.
2) I've the feeling that if we suggest the ISPs to move to a /56, they will
then charge the customers (SOHO, end-users) or create to them a lot of
troubles to get a bigger prefix when this is needed. My feeling is that
today we believe that 8 bits for subnetting is enough, but I think will not
be the case soon and this barrier will then be again a stopper for enabling
innovation. I know this one is somehow not an IETF business, but we must be
worried about that and may be collectively work for the appropriate solution
in the appropriate fora. Otherwise, I will much prefer not to change the /48
to something smaller. Note that I don't think the RIRs are neither a good
fora for making a policy which avoids that the addresses are being charged
at all (hopefully I'm wrong !).

The cost of managing addresses is not a recurrent cost. I mean, it will be
ok to charge for a reasonable setup fee if somebody ask for a /48 instead of
a /56, but charging 12Euros (or even more) per month per address as some
telcos do in EU is a crime.

We need to make sure that anything like that happens with IPv6 ! Otherwise,
we better stop deploying IPv6 now.

Regards,
Jordi




> De: Thomas Narten <[EMAIL PROTECTED]>
> Responder a: <[EMAIL PROTECTED]>
> Fecha: Wed, 13 Jul 2005 23:44:02 +0200
> Para: "ipv6@ietf.org" <ipv6@ietf.org>
> Asunto: FWD: I-D ACTION:draft-narten-ipv6-3177bis-48boundary-00.txt
> 
> Here's an ID for consideration by the IPv6 WG.
> 
> Background:
> 
> Discussion on the more general topic took place at the April ARIN and
> May RIPE meetings.  A good summary of those presentations can be found
> at:
> 
> http://www.ripe.net/ripe/meetings/ripe-50/presentations/ripe50-plenary-wed-ipv
> 6-roundtable-report.pdf
> 
> A more general discussion of the overall topic of IPv6 address
> allocation considerations (the /48 boundary topic is just one piece of
> a larger puzzle) can be found at:
> 
> http://www.ietf.org/internet-drafts/draft-narten-iana-rir-ipv6-considerations-
> 00.txt
> 
> Thomas
> 
> ------- Forwarded Message
> 
> From: [EMAIL PROTECTED]
> To: i-d-announce@ietf.org
> Date: Tue, 12 Jul 2005 15:50:03 -0400
> Subject: I-D ACTION:draft-narten-ipv6-3177bis-48boundary-00.txt
> Reply-To: [EMAIL PROTECTED]
> 
> --NextPart
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 
> Title  : IPv6 Address Allocation to End Sites
> Author(s) : T. Narten, et al.
> Filename : draft-narten-ipv6-3177bis-48boundary-00.txt
> Pages  : 8
> Date  : 2005-7-12
> 
>    This document revisits the IAB/IESG recommendations on the assignment
>    of IPv6 address space to end sites. Specifically, it indicates that
>    changing the default end-site assignment for typical home and SOHO
>    sites from /48 to /56 is consistent with the goals of IPv6 and RFC
>    3177. Although it is for the RIR community to make adjustments to the
>    IPv6 address space allocation and end site assignment policies, the
>    IETF community would be comfortable with RIRs changing the default
>    assignment size to /56 for smaller end sites. This document obsoletes
>    RFC 3177 and reclassifies it as historic.
> 
> A URL for this Internet-Draft is:
> 
http://www.ietf.org/internet-drafts/draft-narten-ipv6-3177bis-48boundary-00.tx>
t
> 
> To remove yourself from the I-D Announcement list, send a message to
> [EMAIL PROTECTED] with the word unsubscribe in the body of the
> message.  
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
> 
> 
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> "get draft-narten-ipv6-3177bis-48boundary-00.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> [EMAIL PROTECTED]
> In the body type:
> "FILE /internet-drafts/draft-narten-ipv6-3177bis-48boundary-00.txt".
> 
> NOTE: The mail server at ietf.org can return the document in
> MIME-encoded form by using the "mpack" utility.  To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command.  To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader.  Different MIME-compliant mail readers
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e. documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
> 
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 
> --NextPart
> Content-Type: Multipart/Alternative; Boundary="OtherAccess"
> 
> --OtherAccess
> Content-Type: Message/External-body; access-type="mail-server";
> server="[EMAIL PROTECTED]"
> 
> Content-Type: text/plain
> Content-ID: <[EMAIL PROTECTED]>
> 
> ENCODING mime
> FILE /internet-drafts/draft-narten-ipv6-3177bis-48boundary-00.txt
> 
> --OtherAccess
> Content-Type: Message/External-body;
> name="draft-narten-ipv6-3177bis-48boundary-00.txt";
> site="ftp.ietf.org"; access-type="anon-ftp";
> directory="internet-drafts"
> 
> Content-Type: text/plain
> Content-ID: <[EMAIL PROTECTED]>
> 
> 
> --OtherAccess--
> 
> --NextPart
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce
> 
> --NextPart--
> 
> ------- End of Forwarded Message
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------




************************************
The IPv6 Portal: http://www.ipv6tf.org

Barcelona 2005 Global IPv6 Summit
Information available at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or 
confidential. The information is intended to be for the use of the 
individual(s) named above. If you are not the intended recipient be aware that 
any disclosure, copying, distribution or use of the contents of this 
information, including attached files, is prohibited.




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to