Re: [v6ops] JANOG34 provides 3.2.1 and 3.2.2

Shishio Tsuchiya <shtsuchi@cisco.com> Mon, 30 June 2014 04:15 UTC

Return-Path: <shtsuchi@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 ACEE51A0160 for <v6ops@ietfa.amsl.com>; Sun, 29 Jun 2014 21:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.552
X-Spam-Level:
X-Spam-Status: No, score=-9.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_55=0.6, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 xOgGd9f3h9jT for <v6ops@ietfa.amsl.com>; Sun, 29 Jun 2014 21:15:17 -0700 (PDT)
Received: from bgl-iport-4.cisco.com (bgl-iport-4.cisco.com [72.163.197.28]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3928B1A014B for <v6ops@ietf.org>; Sun, 29 Jun 2014 21:15:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2525; q=dns/txt; s=iport; t=1404101717; x=1405311317; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=7doGdZxyAPdauJRCoGeK4ExfBOvaJGunVxsJVmWZmwA=; b=aHCeh3MyMS2Uy3ccbyV7aBqNQMfuYFAXH/cmLXCNZI4H11lykRPQbtV9 Q1gUX//xnhvRH1HfHeOwG9vaunpaPDqyVAMaTcyhoAU5PV68R2gUeya6j iQvjiQEDqNcfHqUadDaToWyUp7zveRvtlfGqLWf0iDDwvtl+BFi5ZqoM+ E=;
X-IronPort-AV: E=Sophos;i="5.01,573,1400025600"; d="scan'208";a="11833521"
Received: from vla196-nat.cisco.com (HELO bgl-core-2.cisco.com) ([72.163.197.24]) by bgl-iport-4.cisco.com with ESMTP; 30 Jun 2014 04:15:15 +0000
Received: from SHTSUCHI-M-V1EK.CISCO.COM (dhcp-10-141-41-36.cisco.com [10.141.41.36]) by bgl-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s5U4FDCL021998; Mon, 30 Jun 2014 04:15:14 GMT
Message-ID: <53B0E452.5070202@cisco.com>
Date: Mon, 30 Jun 2014 13:15:14 +0900
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: fred@cisco.com
References: <53AD471B.6070009@cisco.com> <6015024E-05E9-4749-8D85-3943ECDA3111@cisco.com>
In-Reply-To: <6015024E-05E9-4749-8D85-3943ECDA3111@cisco.com>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/wDWBskt-hSSQE_1QWlrbxkBH5TQ
Cc: kshimizu@juniper.net, v6ops@ietf.org, i18n@janog.gr.jp
Subject: Re: [v6ops] JANOG34 provides 3.2.1 and 3.2.2
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: <http://www.ietf.org/mail-archive/web/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: Mon, 30 Jun 2014 04:15:19 -0000

Fred
Thanks.
Report on experience @v6ops is good idea.
Unfortunately I can't go to ietf90 , so I  will ask help to janoger who can attend both and report the experience to v6ops.
Anyway I will post the report to v6ops after janog34.

Regards,
-Shishio



(2014/06/28 9:58), Fred Baker (fred) wrote:
> 
> On Jun 27, 2014, at 3:27 AM, Shishio Tsuchiya <shtsuchi@cisco.com> wrote:
> 
>> Leo and v6ops
>> F.Y.I
>> JANOG(JApan Network Operator's Group) decided to provide ula address to the JANOG34 conference network.
>> http://www.janog.gr.jp/en/index.php?JANOG34_Meeting
>>
>> They will provide 3.2.1. ULA-only Deployment and 3.2.2. ULA along with GUA.
>> http://tools.ietf.org/html/draft-ietf-v6ops-ula-usage-recommendations-02
>>
>> If you would like to confirm something on the network , please let me know.
> 
> Thanks for this.
> 
> I would expect that the key things to prove are the statements in the draft. Also, any observations that might come up would be useful. For example, was it fair to say that the network that was isolated remained isolated? Did using a ULA and a GUA on a globally-accessible network cause any issues? What, if anything, was necessary in the router(s) in question to prevent hosts from using ULA source addresses to connect to GUA addresses? Did hosts in fact form both ULA and GUA-based addresses and use them appropriately when connecting to applications inside and outside the network?
> 
> What one might hope would be that ULA-based addresses were used to connect to other ULA-based addresses, as their bit strings were most similar, and GUA-based addresses were used to connect to other GUA-based addresses, for the same reason. One might hope that ULA prefixes were not announced in BGP without needing extra thought, and that if they were announced, they were not accepted. One might further hope that when a ULA was not announced into a neighboring domain, a packet sent to the ULA prefix didn’t cross the domain boundary.
> 
> Of course, we need to hear about any extra work that was required, and any problems that arose. And we need to understand if the deployment of a ULA prefix necessarily implied the deployment of an IPv6/IPv6 NAT or NAPT. I don’t expect that it will and am certainly not asking for it to, but that expectation has been promoted.
> 
> JANOG will be Wednesday-Friday the week before IETF 90, and v6ops will meet Monday and Tuesday. It would be nice if someone could make a point of reporting on the experiment.