Re: [v6ops] Comment on siit-dc

"Fred Baker (fred)" <fred@cisco.com> Sun, 26 July 2015 06:43 UTC

Return-Path: <fred@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C89F41A8794 for <v6ops@ietfa.amsl.com>; Sat, 25 Jul 2015 23:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level:
X-Spam-Status: No, score=-114.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RI7Xc7gtU2a2 for <v6ops@ietfa.amsl.com>; Sat, 25 Jul 2015 23:43:18 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC5701A8793 for <v6ops@ietf.org>; Sat, 25 Jul 2015 23:43:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3629; q=dns/txt; s=iport; t=1437892997; x=1439102597; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=8Hu+ZEH0fdWXv4g2lpwZCw7y4K7YHZoY//RyF5e5D/g=; b=Y0LiNeM4AyrhTo366eNpkY1mkmoIogjOyeecapdCEK6yXTpnyXiBgPnv mXwfcGpk9CqiNrOKcEe0cN8CzisDAdEQWQ2uNer5g9ZbpGoeamhetKvfr abjeyHufuSRmjZEc+VoBTUUd6GVe+pvBceklSJ8F4mTlOaNX7f7B37RXg E=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AtAwBjgLRV/5BdJa1bgxWBPQa8AgmHcAKBLzgUAQEBAQEBAYEKhCMBAQEDAXkFCwIBCBguMiUCBA4FDogYCM9VAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4tOhQcHgxiBFAWUaQGCN4FXiDKBRYcvkDImg31vgUiBBAEBAQ
X-IronPort-AV: E=Sophos;i="5.15,546,1432598400"; d="asc'?scan'208";a="172494001"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-4.cisco.com with ESMTP; 26 Jul 2015 06:43:17 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t6Q6hHNj024064 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 26 Jul 2015 06:43:17 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.49]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0195.001; Sun, 26 Jul 2015 01:43:16 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Tore Anderson <tore@fud.no>
Thread-Topic: [v6ops] Comment on siit-dc
Thread-Index: AQHQx25Z5Ai8Q9akDUSjS/EtB/+s3w==
Date: Sun, 26 Jul 2015 06:43:16 +0000
Message-ID: <C5AEDEBA-747B-4D87-9532-4C886561DB17@cisco.com>
References: <03B11480-F2E2-4B66-B7A2-1E4824E63D06@cisco.com> <20150726083028.02d6038d@envy.fud.no>
In-Reply-To: <20150726083028.02d6038d@envy.fud.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.213.227]
Content-Type: multipart/signed; boundary="Apple-Mail=_C02DDC55-0ECF-4FCD-A167-33B4940E1DFF"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/TP0Xy0l7cIWkR8TbR770rkf-YAI>
Cc: "draft-ietf-v6ops-siit-dc@tools.ietf.org" <draft-ietf-v6ops-siit-dc@tools.ietf.org>, v6ops list <v6ops@ietf.org>
Subject: Re: [v6ops] Comment on siit-dc
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jul 2015 06:43:19 -0000

> On Jul 26, 2015, at 8:30 AM, Tore Anderson <tore@fud.no> wrote:
> 
> * 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

"when it reaches", or "upon reaching"

>    network infrastructure.  From that point on, it is treated just as if
>    it was traffic from any other IPv6-capable end user. The IPv6

Just a thought: s/is treated just as if it was/is indistinguishable from/

>    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

Works for me. The first suggestion is better English; the second is very optional but is what I think you're trying to say.