IETF Logo Mail Archive

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 20:14 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 9B2D128C13A for <v6ops@core3.amsl.com>; Tue, 5 Apr 2011 13:14:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.343
X-Spam-Level:
X-Spam-Status: No, score=-6.343 tagged_above=-999 required=5 tests=[AWL=0.256, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 C8pP-u1dlzeB for <v6ops@core3.amsl.com>; Tue, 5 Apr 2011 13:14:04 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id BEDE428C141 for <v6ops@ietf.org>; Tue, 5 Apr 2011 13:14:04 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by slb-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p35KFfWS007277 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 5 Apr 2011 13:15:42 -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 p35KFf0K003269; Tue, 5 Apr 2011 15:15:41 -0500 (CDT)
Received: from XCH-NWHT-09.nw.nos.boeing.com (xch-nwht-09.nw.nos.boeing.com [130.247.25.115]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p35KFcB4003127 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 5 Apr 2011 15:15:40 -0500 (CDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-09.nw.nos.boeing.com ([130.247.25.115]) with mapi; Tue, 5 Apr 2011 13:15:39 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: IPv6 Ops WG <v6ops@ietf.org>
Date: Tue, 05 Apr 2011 13:15:37 -0700
Thread-Topic: [v6ops] Fwd: I-DAction:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt
Thread-Index: AcvwqhO9BdUyiwMRQ4qcBPNNIw4tOABZkpawAG4ikyA=
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C691F0382@XCH-NW-01V.nw.nos.boeing.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.com> <E1829B60731D1740BB7A0626B4FAF0A65C69181DE0@XCH-NW-01V.nw.nos.boeing.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65C69181DE0@XCH-NW-01V.nw.nos.boeing.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
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 20:14:05 -0000

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

v2.23.0 | Report a Bug | By Email