IETF Logo Mail Archive

Re: [v6ops] Fwd:I-DAction:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt

Fred Baker <fred@cisco.com> Tue, 05 April 2011 22:28 UTC

Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2773E3A67F3 for <v6ops@core3.amsl.com>; Tue, 5 Apr 2011 15:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.004
X-Spam-Level:
X-Spam-Status: No, score=-110.004 tagged_above=-999 required=5 tests=[AWL=-0.320, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dHI3tdr2+5W2 for <v6ops@core3.amsl.com>; Tue, 5 Apr 2011 15:28:38 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 407A63A66B4 for <v6ops@ietf.org>; Tue, 5 Apr 2011 15:28:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=3930; q=dns/txt; s=iport; t=1302042622; x=1303252222; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=PQ2LbobuYwCCAWHiV2zPnogmKVRci8em1peMDuDPddU=; b=leABxudBledEM/WKxh7x+c7zTAknDzsHjsrqj9wAJYiFvTRVQeACYjyq RWCwctIIWB1TDSvH+I52tfb0CxXTlqSH446AFMAhmH4K+KtxbJp9VDnYz 8zsYxDZwrN7ARuxJoC0Bpu6TuEphoa8+2xe9KyJC6EgU6D3AwG0bc2oJk k=;
X-IronPort-AV: E=Sophos;i="4.63,307,1299456000"; d="scan'208";a="82317954"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 05 Apr 2011 22:30:21 +0000
Received: from Freds-Computer.local (dhcp-10-61-105-97.cisco.com [10.61.105.97]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p35MU7Bm017395; Tue, 5 Apr 2011 22:30:15 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Wed, 06 Apr 2011 00:30:18 +0200
X-PGP-Universal: processed; by Freds-Computer.local on Wed, 06 Apr 2011 00:30:18 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65C691F0434@XCH-NW-01V.nw.nos.boeing.com>
Date: Wed, 06 Apr 2011 00:29:46 +0200
Message-Id: <856E17EA-E3BA-47CE-A1D9-DD10F276991A@cisco.com>
References: <959B73D2-A53C-4682-BB4B-ADFB71CA7906@cisco.com><14D633B3-6087-4 303-8A84-0D84D11CCFA4@cisco.com><E1829B60731D1740BB7A0626B4FAF0A65C69181C9A @XCH-NW-01V.nw.nos.boeing.com><8AD676EE-6C4D-4C7B-B5AD-4042476EB3DE@cisco.c om><E1829B60731D1740BB7A0626B4FAF0A65C69181DE0@XCH-NW-01V.nw.nos.boeing.com ><E1829B60731D1740BB7A0626B4FAF0A65C691F0382@XCH-NW-01V.nw.nos.boeing.com> <5B6B2B64C9FE2A489045EEEADDAFF2C301391307@XMB-RCD-109.cisco.com> <5B6B2B64C9FE2A489045EEEADDAFF2C301391380@XMB-RCD-109.cisco.com> <E1829B60731D1740BB7A0626B4FAF0A65C691F0434@XCH-NW-01V.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] Fwd:I-DAction:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 05 Apr 2011 22:28:40 -0000

Isn't cpe-router-bis is about a native IPv6 residential/SOHO network? What would ISATAP do in a native IPv6 network?

On Apr 5, 2011, at 11:59 PM, Templin, Fred L wrote:
> Hi Hemant,
> 
> I have no way of knowing how many home or soho networks
> use ISATAP today, however I do know that there are many
> (millions of?) hosts that would automatically enable
> ISATAP if it were available in the home/soho network.
> 
> Thanks - Fred
> fred.l.templin@boeing.com 
> 
>> -----Original Message-----
>> From: Hemant Singh (shemant) [mailto:shemant@cisco.com] 
>> Sent: Tuesday, April 05, 2011 2:42 PM
>> To: Hemant Singh (shemant); Templin, Fred L; IPv6 Ops WG
>> Subject: RE: [v6ops] 
>> Fwd:I-DAction:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt
>> 
>> Fred,
>> 
>> One feedback from the design team was to ask how many home or soho
>> networks use ISATAP today before the team would decide to add 
>> ISATAP to
>> the bis document?  
>> 
>> Thanks,
>> 
>> Hemant
>> 
>> -----Original Message-----
>> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
>> Of Hemant Singh (shemant)
>> Sent: Tuesday, April 05, 2011 4:34 PM
>> To: Templin, Fred L; IPv6 Ops WG
>> Subject: Re: [v6ops]
>> Fwd:I-DAction:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt
>> 
>> Fred,
>> 
>> Thanks for the text.  I will run your email by our IPv6 CE 
>> Router design
>> team and solicit feedback from them for ISATAP in the IPv6 CE Router
>> specification.
>> 
>> Cheers,
>> 
>> Hemant
>> 
>> -----Original Message-----
>> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
>> Of Templin, Fred L
>> Sent: Tuesday, April 05, 2011 4:16 PM
>> To: IPv6 Ops WG
>> Subject: Re: [v6ops] Fwd:
>> I-DAction:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt
>> 
>> I would like to propose a new section for this draft to
>> cover the use of transition technologies within the end
>> user LAN side network. See below for proposed text:
>> 
>> Fred
>> fred.l.templin@boeing.com
>> 
>> --- cut here ---
>> 
>> 5.5.3  ISATAP
>> 
>>   The IPv6 CE Router can be used to offer IPv6 services to nodes
>>   on IPv4-only segments within the end user LAN. ISATAP [RFC5214]
>>   provides for intra-site encapsulation of IPv6 packets over IPv4
>>   networks that connect to the IPv6 Internet via one or more IPv6
>>   CE Routers configured as site border routers. The IPv6 CE Router
>>   sub-delegates portions of its IPv6 prefixes for assignment to
>>   nodes on the ISATAP link and/or to the ISATAP link itself. 
>> 
>>   ISATAP requirements:
>> 
>>   ISA-1:  If the IPv6 CE Router implements ISATAP functionality, the
>>           CE Router LAN interface MUST support at least one ISATAP
>>           virtual interface and ISATAP router functionality as
>>           specified in [RFC5214].
>> 
>>   ISA-2:  If the IPv6 CE Router implements ISATAP functionality, it
>>           MUST arrange to add itself to the ISATAP Potential Router
>>           List (PRL) for the LAN.
>> 
>>   ISA-3:  When the LAN contains legacy ISATAP nodes that support
>>           only SLAAC, the IPv6 CE router MUST advertise IPv6 prefixes
>>           on the ISATAP interface.
>> 
>>   ISA-4:  The CE router MUST be configured in a manner that ensures
>>           that no IPv6 routing loops are enabled via the ISATAP
>>           interface [draft-ietf-v6ops-tunnel-loops].
>> _______________________________________________
>> 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
>> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email