Re: [v6ops] Comment on siit-dc

[Tore Anderson <[e-mail]>]

* Fred Baker (fred)

> The abstract reads:
> 
>    This document describes the use of the Stateless IP/ICMP Translation
>    (SIIT) algorithm in an IPv6 Internet Data Centre (IDC).  In this
>    deployment model, traffic from legacy IPv4-only clients on the
>    Internet is translated to IPv6 when reaches the IDC operator's
>    network infrastructure.  From that point on, it is treated just as if
>    it was traffic from any other IPv6-capable end user.  This
>    facilitates a single-stack IPv6-only network infrastructure, as well
>    as efficient utilisation of public IPv4 addresses.
> 
>    The primary audience is IDC operators who are deploying IPv6, running
>    out of available IPv4 addresses, and/or feel that dual stack causes
>    undesirable operational complexity.
> 
> I see what you're saying, but can read it as specifying how an RFC
> 6052 address might be used, when you're specifying the use of
> siit-eam. May I suggest tweaking the abstract to clarify that?

Point taken. How about:

    This document describes the use of the Stateless IP/ICMP Translation
    (SIIT) algorithm in an IPv6 Internet Data Centre (IDC).  In this
    deployment model, traffic from legacy IPv4-only clients on the
    Internet is translated to IPv6 when reaches the IDC operator's
    network infrastructure.  From that point on, it is treated just as if
    it was traffic from any other IPv6-capable end user. The IPv6
    endpoints may be numbered using arbitrary (non-IPv4-translatable)
    IPv6 addresses. This facilitates a single-stack IPv6-only network
    infrastructure, as well as efficient utilisation of public IPv4
    addresses.

    The primary audience is IDC operators who are deploying IPv6,
    running out of available IPv4 addresses, and/or feel that dual
    stack causes undesirable operational complexity.

...?

Tore