[v6ops] 6204bis and WAN disappearing
"Dan Wing" <dwing@cisco.com> Tue, 21 February 2012 23:49 UTC
Return-Path: <dwing@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF69C21E8059 for <v6ops@ietfa.amsl.com>; Tue, 21 Feb 2012 15:49:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.65
X-Spam-Level:
X-Spam-Status: No, score=-108.65 tagged_above=-999 required=5 tests=[AWL=1.949, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 703xRvxt74FN for <v6ops@ietfa.amsl.com>; Tue, 21 Feb 2012 15:49:52 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 80B8721E8033 for <v6ops@ietf.org>; Tue, 21 Feb 2012 15:49:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1712; q=dns/txt; s=iport; t=1329868192; x=1331077792; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=ADg6em/3fgGkHkzmvUUzrA+l5idjQB/2IqSJAr+3/Hs=; b=M2Epd95e7vWdxvGW6nXuybGUWm4Hv7eeR6Kc0sVNT0udyQaoEp+bVwHT HpxyIbm89OVmuUJk6reVz6jdS1UKzOZKQO2cds+p0h+C8SNzqKDjIAYEB erLCnLVYFM4M/ncgSWcbdvN3aPQE3RTQs1jaYA1uMXJTROH9ld5glXbAS M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAIssRE+rRDoJ/2dsb2JhbABEok+Pd4EHgXoICgEXED8NBRhQIxwBBB4Xh2egDgGXLYt2GhIEAQEsAwsDAgEBAYQRJoMeBIhPhQeacA
X-IronPort-AV: E=Sophos;i="4.73,460,1325462400"; d="scan'208";a="31655314"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 21 Feb 2012 23:49:52 +0000
Received: from dwingWS ([10.154.160.50]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q1LNnqRI027934; Tue, 21 Feb 2012 23:49:52 GMT
From: Dan Wing <dwing@cisco.com>
To: v6ops@ietf.org
Date: Tue, 21 Feb 2012 15:49:52 -0800
Message-ID: <021601ccf0f3$812952f0$837bf8d0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Aczw84ECxzzuwPVYQ0aM/GWBoA4FXQ==
Content-Language: en-us
Cc: draft-ietf-v6ops-6204bis@tools.ietf.org
Subject: [v6ops] 6204bis and WAN disappearing
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 21 Feb 2012 23:49:57 -0000
Reading draft-ietf-v6ops-6204bis-05, I couldn't determine what the CE router should do if, after it acquires an IPv6 prefix from its WAN interface, the WAN interface later goes down. Requirement G-4 in the specification (http://tools.ietf.org/html/draft-ietf-v6ops-6204bis-05#section-4.1) requires the CE router (immediately?) withdraw the prefix on the LAN interface, but if this text (from draft-ietf-v6ops-6204bis-05) is true: 1. Link-local addresses may be insufficient for allowing IPv6 applications to communicate with each other in the end-user network. The IPv6 CE router will need to enable this communication by providing globally scoped unicast addresses or ULAs [RFC4193], whether or not WAN connectivity exists. then withdrawing the globally scoped unicast addresses will break communication within the home. This means if my WAN link goes down, IPv6 streaming between my NAS and my speakers breaks which ruins my dinner party. Can draft-ietf-v6ops-6204bis be more precise describing what happens when the WAN link fails (should the globally scoped prefix be withdrawn on the LAN? Immediately? After several days? What about after a reboot of the CPE?), and can it be more precise to discuss if the CE router has to provide a globally scoped unicast address or has to provide ULA, or has to provide both. As written, devices in the home that rely on the globally-scoped address will fail if the WAN link fails, and it should not be necessary for host and CE router implementers to read the tea leaves of draft-ietf-v6ops-6204bis that ULA is necessary for successful operation of home network equipment when the WAN fails. -d
- [v6ops] 6204bis and WAN disappearing Dan Wing
- Re: [v6ops] 6204bis and WAN disappearing Rémi Després
- Re: [v6ops] 6204bis and WAN disappearing Lorenzo Colitti
- Re: [v6ops] 6204bis and WAN disappearing Tore Anderson
- Re: [v6ops] 6204bis and WAN disappearing Rajiv Asati (rajiva)
- Re: [v6ops] 6204bis and WAN disappearing STARK, BARBARA H
- Re: [v6ops] 6204bis and WAN disappearing Timothy Winters
- Re: [v6ops] 6204bis and WAN disappearing Rémi Després
- Re: [v6ops] 6204bis and WAN disappearing Dan Wing
- Re: [v6ops] 6204bis and WAN disappearing Weil, Jason
- Re: [v6ops] 6204bis and WAN disappearing Ole Trøan
- Re: [v6ops] 6204bis and WAN disappearing Ted Lemon
- Re: [v6ops] 6204bis and WAN disappearing Weil, Jason
- Re: [v6ops] 6204bis and WAN disappearing Rémi Després
- Re: [v6ops] 6204bis and WAN disappearing Ted Lemon
- Re: [v6ops] 6204bis and WAN disappearing Ted Lemon
- Re: [v6ops] 6204bis and WAN disappearing Weil, Jason
- Re: [v6ops] 6204bis and WAN disappearing STARK, BARBARA H
- Re: [v6ops] 6204bis and WAN disappearing STARK, BARBARA H
- Re: [v6ops] 6204bis and WAN disappearing Ted Lemon
- Re: [v6ops] 6204bis and WAN disappearing Brian E Carpenter
- Re: [v6ops] 6204bis and WAN disappearing STARK, BARBARA H
- Re: [v6ops] 6204bis and WAN disappearing Ted Lemon
- Re: [v6ops] 6204bis and WAN disappearing Hemant Singh (shemant)
- Re: [v6ops] 6204bis and WAN disappearing STARK, BARBARA H
- Re: [v6ops] 6204bis and WAN disappearing Ole Trøan
- Re: [v6ops] 6204bis and WAN disappearing Weil, Jason
- Re: [v6ops] 6204bis and WAN disappearing Rémi Després
- Re: [v6ops] 6204bis and WAN disappearing Rémi Després
- Re: [v6ops] 6204bis and WAN disappearing Rémi Després
- Re: [v6ops] 6204bis and WAN disappearing Ted Lemon
- Re: [v6ops] 6204bis and WAN disappearing Rémi Després
- Re: [v6ops] 6204bis and WAN disappearing Wuyts Carl
- Re: [v6ops] 6204bis and WAN disappearing Rémi Després
- Re: [v6ops] 6204bis and WAN disappearing Ralph Droms
- Re: [v6ops] 6204bis and WAN disappearing Timothy Winters
- Re: [v6ops] 6204bis and WAN disappearing Rémi Després
- Re: [v6ops] 6204bis and WAN disappearing Ted Lemon
- Re: [v6ops] 6204bis and WAN disappearing Brian E Carpenter
- Re: [v6ops] 6204bis and WAN disappearing Mark Andrews
- Re: [v6ops] 6204bis and WAN disappearing Ted Lemon
- Re: [v6ops] 6204bis and WAN disappearing james woodyatt
- Re: [v6ops] 6204bis and WAN disappearing Ted Lemon
- Re: [v6ops] 6204bis and WAN disappearing Rémi Després
- Re: [v6ops] 6204bis and WAN disappearing Ralph Droms
- Re: [v6ops] 6204bis and WAN disappearing HahnC
- Re: [v6ops] 6204bis and WAN disappearing Rajiv Asati (rajiva)
- Re: [v6ops] 6204bis and WAN disappearing HahnC
- Re: [v6ops] 6204bis and WAN disappearing STARK, BARBARA H
- Re: [v6ops] 6204bis and WAN disappearing Ole Trøan
- Re: [v6ops] 6204bis and WAN disappearing Brian E Carpenter
- Re: [v6ops] 6204bis and WAN disappearing Hemant Singh (shemant)