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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 05 April 2011 22:47 UTC

Return-Path: <Fred.L.Templin@boeing.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 1D49328C160 for <v6ops@core3.amsl.com>; Tue, 5 Apr 2011 15:47:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.886
X-Spam-Level:
X-Spam-Status: No, score=-5.886 tagged_above=-999 required=5 tests=[AWL=-0.202, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315]
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 eUUqiu0UOa48 for <v6ops@core3.amsl.com>; Tue, 5 Apr 2011 15:47:54 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 9D6D828C15C for <v6ops@ietf.org>; Tue, 5 Apr 2011 15:47:54 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p35MnUV1025533 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 5 Apr 2011 15:49:31 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p35MnUpD018463; Tue, 5 Apr 2011 17:49:30 -0500 (CDT)
Received: from XCH-NWHT-06.nw.nos.boeing.com (xch-nwht-06.nw.nos.boeing.com [130.247.25.110]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p35MnTrQ018431 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 5 Apr 2011 17:49:30 -0500 (CDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-06.nw.nos.boeing.com ([130.247.25.110]) with mapi; Tue, 5 Apr 2011 15:49:28 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fred Baker <fred@cisco.com>
Date: Tue, 05 Apr 2011 15:49:28 -0700
Thread-Topic: [v6ops] Fwd:I-DAction:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt
Thread-Index: Acvz4Q8n0FNPjHZLSOC0dAwAQxTsaQAAYSGA
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C691F0469@XCH-NW-01V.nw.nos.boeing.com>
References: <959B73D2-A53C-4682-BB4B-ADFB71CA7906@cisco.com><14D633B3-6087-4 303-8A84-0D84D11CCFA4@cisco.com><E1829B60731D1740BB7A0626B4FAF0A65C69181C9 A @XCH-NW-01V.nw.nos.boeing.com><8AD676EE-6C4D-4C7B-B5AD-4042476EB3DE@cisco.c om><E1829B60731D1740BB7A0626B4FAF0A65C69181DE0@XCH-NW-01V.nw.nos.boeing.co m ><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> <856E17EA-E3BA-47CE-A1D9-DD10F276991A@cisco.com>
In-Reply-To: <856E17EA-E3BA-47CE-A1D9-DD10F276991A@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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:47:56 -0000

Hi Fred, 

> -----Original Message-----
> From: Fred Baker [mailto:fred@cisco.com] 
> Sent: Tuesday, April 05, 2011 3:30 PM
> To: Templin, Fred L
> Cc: Hemant Singh (shemant); IPv6 Ops WG
> Subject: Re: [v6ops] 
> Fwd:I-DAction:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt
> 
> Isn't cpe-router-bis is about a native IPv6 residential/SOHO 
> network?

Well, Section 3.1 of draft-ietf-v6ops-ipv6-cpe-router-09
seems to acknowledge the existence of current IPv4 End-user
networks, and that: "It is not expected that an end-user
will change their existing network topology with the
introduction of IPv6".

It seems therefore that there will be a class of end
user networks that would benefit from an intra-site
IPv6/IPv4 transition technology.

> What would ISATAP do in a native IPv6 network?

The host would prefer native IPv6 over ISATAP. But,
not all home/soho networks are set up for native IPv6.

Thanks - Fred
fred.l.templin@boeing.com

> 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
> 
>