[LACNIC/Politicas] Fwd: [ipv6-wg] RIPE Policy vs IETF RFC

Arturo Servin arturo.servin at gmail.com
Tue Jun 14 00:48:30 BRT 2016


Creo que son 2 cosas distintas pero puedo estar equivocado.

Una es la asignacion minima para un usuario (RIPE) y la otra es que el
proceso de ruteo debe ser capaz de mover paquetes de subredes de cualquier
longitud.

Slds
as

On Mon, 13 Jun 2016 at 06:27 Alejandro Acosta <
alejandroacostaalamo at gmail.com> wrote:

> Hola,
>
>   Me atrevo a reenviar este correo a esta lista.
>
>   Sería interesante escuchar algún feedback/comentario de los suscritos,
> claro, relacionado a Lacnic preferiblemente :-)
>
>
> Saludos,
>
>
> Alejandro,
>
>
>
> -------- Mensaje reenviado --------
> Asunto:         [ipv6-wg] RIPE Policy vs IETF RFC
> Fecha:  Mon, 13 Jun 2016 11:53:18 +0200
> De:     Nathalie Trenaman <nathalie at ripe.net>
> Para:   ipv6-wg at ripe.net
>
>
>
> Dear colleagues,
>
> As you might know, the current IPv6 policy states very clear that
> assignments to customers must be a minimum of a /64.
>
> 5.4.1. Assignment address space size
>
> End Users are assigned an End Site assignment from their LIR or ISP. The
> size of the assignment is a local decision for the LIR or ISP to make,
> using a minimum value of a /64 (only one subnet is anticipated for the End
> Site).
>
> https://www.ripe.net/publications/docs/ripe-655
>
> On the other hand, a while ago, RFC7608 (BCP198) was published, stating:
>
> 2.  Recommendation
>    IPv6 implementations MUST conform to the rules specified in
>    Section 5.1 of [RFC4632].
>
>    Decision-making processes for forwarding MUST NOT restrict the length
>    of IPv6 prefixes by design.  In particular, forwarding processes MUST
>    be designed to process prefixes of any length up to /128, by
>    increments of 1.
>
> In practice, this means that the RFC suggests that a customer can get an
> IPv6 assignment of any size, while the RIPE policy says the minimum should
> be a /64.
> I’m interested to know what the community thinks about this and if
> alignment between this RFC and the RIPE policy is needed.
>
>
> Nathalie Künneke-Trenaman
> IPv6 Program Manager
> RIPE NCC
>
>
>
> _______________________________________________
> Politicas mailing list
> Politicas at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/politicas
>



More information about the Politicas mailing list