Re: [v6ops] IANA assigned prefix for IPv6 benchmarking

"GEORGESCU LIVIU MARIUS" <liviumarius-g@is.naist.jp> Sat, 25 July 2015 10:37 UTC

Return-Path: <liviumarius-g@is.naist.jp>
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 221321A88F3 for <v6ops@ietfa.amsl.com>; Sat, 25 Jul 2015 03:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.599
X-Spam-Level:
X-Spam-Status: No, score=0.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 sDm7Kv5OlIcQ for <v6ops@ietfa.amsl.com>; Sat, 25 Jul 2015 03:37:17 -0700 (PDT)
Received: from mailrelay22.naist.jp (mailrelay22.naist.jp [IPv6:2001:200:16a:50::91]) by ietfa.amsl.com (Postfix) with ESMTP id 844661A0158 for <v6ops@ietf.org>; Sat, 25 Jul 2015 03:37:17 -0700 (PDT)
Received: from mailpost22.naist.jp (mailscan22.naist.jp [163.221.80.59]) by mailrelay22.naist.jp (Postfix) with ESMTP id 16F0361C; Sat, 25 Jul 2015 19:37:16 +0900 (JST)
Received: from naist.jp (webmail21-a.naist.jp [163.221.80.53]) by mailpost22.naist.jp (Postfix) with ESMTP id F3E3861B; Sat, 25 Jul 2015 19:37:15 +0900 (JST)
Received: from [127.0.0.1] (Forwarded-For: ::ffff:89.248.140.10) by webmail21-a.naist.jp (mshttpd); Sat, 25 Jul 2015 12:37:15 +0200
From: GEORGESCU LIVIU MARIUS <liviumarius-g@is.naist.jp>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, v6ops@ietf.org
Message-ID: <6bf0c04ef47e.55b382fb@naist.jp>
Date: Sat, 25 Jul 2015 12:37:15 +0200
X-Mailer: Oracle Communications Messenger Express 7.0.5.35.0 64bit (built Mar 31 2015)
MIME-Version: 1.0
Content-Language: en
X-Accept-Language: en
Priority: normal
In-Reply-To: <6c50d867e570.55b366a4@naist.jp>
References: <6b60e612c4f0.55b20091@naist.jp> <6c008406e2af.55b200cf@naist.jp> <6c00eec89ab8.55b2010d@naist.jp> <6bf095d99dae.55b2014a@naist.jp> <6b50ff96a9ad.55b20188@naist.jp> <6c50a92cde54.55b201c6@naist.jp> <6c50be138e83.55b20205@naist.jp> <6bf08db1e13f.55b20243@naist.jp> <6bf0f7dbdadf.55b20280@naist.jp> <6bf0898ffbd5.55b21ea8@naist.jp> <55B29026.1070906@gmail.com> <6b70d3cfd2f6.55b365ea@naist.jp> <6b70bfbf8107.55b36628@naist.jp> <6c30a2fefa4c.55b36666@naist.jp> <6c50d867e570.55b366a4@naist.jp>
Content-Type: multipart/alternative; boundary="--7bf5644769e853851747"
X-TM-AS-MML: No
X-TM-AS-Product-Ver: IMSS-7.1.0.1392-8.0.0.1202-21702.006
X-TM-AS-Result: No--24.547-5.0-31-10
X-imss-scan-details: No--24.547-5.0-31-10
X-TMASE-MatchedRID: 2BgX6Efr+StjyIn1sobvhavnfoenSIXeRphO9iDI3+WJVA+ukO+5MeLd prnA5EQR+KgiyLtJrSD1yFIyxT4ny1YWwxB9tw0TMIZH9N34VaGdvX66iOkhuEIw4Xa9LAtM8eS mTJSmEv1+Mk6ACsw4JlyPhb2isyDdREKjiqASiUTcN9P0Iqci4L8elP/2IwgBYY3ozW+Engd2aF FWhkT3QJ20dShmm+V5FFn/3AEyEaytEaJoVjyWkJb/mTnkM/SIHDnwvr6B+jSPmsTSpXoLhIoLo ibgjVEXi/ymJ2FVg5SISI683skDCj28dBzwO9dQcQHFIHvz5Cu6H+0z6Sb8PLwRFHRPw4UGPluj dkswUwfKi5Jqc8KFNL9rZX4J6klH8R1CbhYofuni8zVgXoAltk77e4Y1xq/3tTBdP6jTSDcelJ9 TflOPDWWGEPQRVcN48BdxbGBwPnKxmoQAAdv2lEUYJ3RLQ0KyLQSRR+42XxMiYYwXiyivaTL/Sr uSxM2vyXhrwNW2QkNgO21BQaodlQ==
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/hk3032TcEuH3xiEM_0-wC1JOhwg>
Subject: Re: [v6ops] IANA assigned prefix for IPv6 benchmarking
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: Sat, 25 Jul 2015 10:37:19 -0000

If respecting the recommendations of RFC5180 is desired I think the following note in RFC5180 is relevant:

" Note: Similar to RFC 2544(https://tools.ietf.org/html/rfc2544) avoiding the use of RFC 1918(https://tools.ietf.org/html/rfc1918) address space

 for benchmarking tests, this document does not recommend the use of RFC 4193(https://tools.ietf.org/html/rfc4193) [4(https://tools.ietf.org/html/rfc5180#ref-4)] (Unique Local Addresses) in order to minimize the 

 possibility of conflicts with operational traffic."

which in my understanding does not recommend the use of ULA s.

Best regards,
Marius 

On 07/24/15, Alexandru Petrescu  <alexandru.petrescu@gmail.com> wrote:
> 
> 
> 
> Le 24/07/2015 11:16, GEORGESCU LIVIU MARIUS a écrit :
> >Hello v6ops,
> >
> >Related to the question that came up in Stuart Cheshire's presentation
> >about the prefix used for benchmarking, RFC5180(with errata) "IPv6
> >Benchmarking Methodology for Network Interconnect Devices" (which might
> >not apply here) states: "The IANA has assigned 2001:0002::/48 for IPv6
> >benchmarking, which is a 48-bit prefix from the RFC 4773 pool."
> >I hope this helps.
> 
> To me, this is an additional reason to think that it is good to use ULAs (not 2001:s or Teredos) behind any form of NATxy.
> 
> But I heard there may be good reasons to avoid ULA in NAT64. Not sure which.
> 
> Alex
> 
> >
> >Best regards,
> >Marius
> >
> >
> >_______________________________________________
> >v6ops mailing list
> >v6ops@ietf.org
> >https://www.ietf.org/mailman/listinfo/v6ops
> >
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>