[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: draft-narten-ipv6-3177bis-48boundary-02.txt
Hi all,
I've reviewed this document and my comments are as follows.
1. Introduction
"giving out an excessive". I think we need to define excessive and/or say if
this is an objective or subjective perception.
A general comment/opinion. I don't think this document should be published
as is, because it provides a bad message to the market about IPv6 assignment
recommendations not being stable. I will be in favor of a "smaller" revision
of RFC3177, not so much disruptive as this one, but in the other way around,
discouraging /128 and /64 assignments.
I think the motivations behind the /48 are still valid and one of the main
goals of IPv6 addressing space is to ensure enough space to end-users, which
is only ensured with a clear boundary recommendation.
Furthermore, the lack of a clear boundary disrupts the RFC3177 goal of
ensuring a consistent subnet to facilitate management and renumbering. In
practice receiving a new assignment from and ISP w/o a specific
recommendation will be a big source of troubles if different ISPs decide to
do different things. Take the case of a user moving from an existing ISP
with today provides a /48 to a new one.
In addition, as an end user, it provides a recommendation to ISPs to provide
a reduced service in terms of the number of subnets, instead of the actual
/48 recommendations (with a clear example for /56), which I think is very
bad, especially when it is based in a subjective view of "excessive".
I also think that the lack of clarity in stating that more than a single /64
is required in most of the cases is going to be wrongly taken as a "go for
/64".
Regards,
Jordi
> De: Thomas Narten <narten@us.ibm.com>
> Responder a: <ipv6-bounces@ietf.org>
> Fecha: Wed, 12 Jul 2006 09:30:27 -0400
> Para: <ipv6@ietf.org>
> Asunto: FWD: draft-narten-ipv6-3177bis-48boundary-02.txt
>
> ------- Forwarded Message
>
> From: Thomas Narten <narten@us.ibm.com>
> To: v6ops@ops.ietf.org
> Date: Wed, 12 Jul 2006 09:26:27 -0400
> Subject: draft-narten-ipv6-3177bis-48boundary-02.txt
>
> FYI, draft-narten-ipv6-3177bis-48boundary-02.txt was submitted just
> prior to the ID cutoff, and the authors believe it is ready for
> publication as an RFC. We are in discussion with the ADs about having
> the document shepherded through the IESG as an informational document.
> Note that this document would formally replace RFC3177.
>
> Comments welcome of course!
>
> Thomas
>
> ------- 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
Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org
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.