IETF Logo Mail Archive

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

"Hemant Singh (shemant)" <shemant@cisco.com> Tue, 05 April 2011 21:39 UTC

Return-Path: <shemant@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 829543A67E1 for <v6ops@core3.amsl.com>; Tue, 5 Apr 2011 14:39:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.348
X-Spam-Level:
X-Spam-Status: No, score=-10.348 tagged_above=-999 required=5 tests=[AWL=-0.349, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
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 mhUkl5kLC8fb for <v6ops@core3.amsl.com>; Tue, 5 Apr 2011 14:39:49 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 73BD33A67D8 for <v6ops@ietf.org>; Tue, 5 Apr 2011 14:39:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=2723; q=dns/txt; s=iport; t=1302039693; x=1303249293; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=SnB0txyceEKvfIanlzNQVkIaM9xzt9PoSBoHSHtfmGk=; b=LCNnVifPdxWVA7D3VDKQ7Jr35La7S46CWlK0sjcTbmit6DwT5F+uZVKy Bf3VW8ZWObXFwTjFa4HGhdieqSU3sOzClpmPn2MsPmX21SlR1X7531Umz KDFQzEO4zz1Ud8NOBvYCiI4HuhXuCt0ms7sEfCEAtOLBr1uuPhjfO7C63 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvIAAMuLm02tJXG9/2dsb2JhbACYJ41Id6cSnB+FbASFR4s/
X-IronPort-AV: E=Sophos;i="4.63,307,1299456000"; d="scan'208";a="331287514"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by sj-iport-2.cisco.com with ESMTP; 05 Apr 2011 21:41:32 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id p35LfW6V014700; Tue, 5 Apr 2011 21:41:32 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 5 Apr 2011 16:41:32 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 05 Apr 2011 16:41:30 -0500
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C301391380@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C301391307@XMB-RCD-109.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [v6ops] Fwd:I-DAction:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt
Thread-Index: AcvwqhO9BdUyiwMRQ4qcBPNNIw4tOABZkpawAG4ikyAAAeoMQAACOq5g
References: <959B73D2-A53C-4682-BB4B-ADFB71CA7906@cisco.com><14D633B3-6087-4303-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><E1829B60731D1740BB7A0626B4FAF0A65C691F0382@XCH-NW-01V.nw.nos.boeing.com> <5B6B2B64C9FE2A489045EEEADDAFF2C301391307@XMB-RCD-109.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, IPv6 Ops WG <v6ops@ietf.org>
X-OriginalArrivalTime: 05 Apr 2011 21:41:32.0581 (UTC) FILETIME=[3AD77550:01CBF3DA]
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 21:39:50 -0000

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

v2.23.0 | Report a Bug | By Email