Re: [v6ops] senario of draft-zhang-v6ops-ipv6oa-iwf-00.txt

"Fred Baker (fred)" <fred@cisco.com> Tue, 07 August 2012 15:36 UTC

Return-Path: <fred@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 6757A21F8720 for <v6ops@ietfa.amsl.com>; Tue, 7 Aug 2012 08:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.615
X-Spam-Level:
X-Spam-Status: No, score=-109.615 tagged_above=-999 required=5 tests=[AWL=-0.816, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, J_CHICKENPOX_54=0.6, J_CHICKENPOX_75=0.6, 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 bCoa4o-JC5Hf for <v6ops@ietfa.amsl.com>; Tue, 7 Aug 2012 08:36:22 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id C89D221F871E for <v6ops@ietf.org>; Tue, 7 Aug 2012 08:36:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=3018; q=dns/txt; s=iport; t=1344353781; x=1345563381; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=1Wm5d+9N52pmDrCnFqycXIpD+2nGq0OlLeci2wlqxT4=; b=Sq+Z+GAgsEL0P2UyDklZSQWDsaQKBVM0inrLCg1BaU4TAFhzQeEP98K+ 3AOdaYslMswYcoFTVkiPUI0m2j8qux8XAxMfatDC6LCr9SLxpBn8XtSW7 etlRMXUVnzYZf2D3YSD87T7BO90okadB47lp9tXJo+rKZ+hMSOUp5HfHG I=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EALM0IVCtJV2b/2dsb2JhbABFuUaBB4IgAQEBAwESAWYFCwIBCBguMiUCBAoEExSHZQabXqBaiw+GDWADjliBIIVQjiaBZoJf
X-IronPort-AV: E=Sophos; i="4.77,727,1336348800"; d="asc'?scan'208"; a="109232781"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-4.cisco.com with ESMTP; 07 Aug 2012 15:36:16 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q77FaGA8028174 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 7 Aug 2012 15:36:16 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.97]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0298.004; Tue, 7 Aug 2012 10:36:16 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "zveno.chen" <zveno.chen@gmail.com>
Thread-Topic: senario of draft-zhang-v6ops-ipv6oa-iwf-00.txt
Thread-Index: AQHNdLJh1zIqGiTXOEWRJLLUlZiwFw==
Date: Tue, 07 Aug 2012 15:36:15 +0000
Message-ID: <B830C0C1-5FC9-43B3-81F2-01F0A96BA9C0@cisco.com>
References: <201208072051330785547@gmail.com>
In-Reply-To: <201208072051330785547@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.19.64.116]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19090.005
x-tm-as-result: No--22.913300-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/signed; boundary="Apple-Mail=_5A975D51-772D-44E8-AE38-86E6F91B992C"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] senario of draft-zhang-v6ops-ipv6oa-iwf-00.txt
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, 07 Aug 2012 15:36:23 -0000

On Aug 7, 2012, at 5:51 AM, zveno.chen wrote:
>    The senario of IPv6oA is exist in Chinatelecom network. In our IPV4 network some of our customers uses a service called ATM private-Line. In this service, user's CPE device connect to core network by IPoA (PVC/SVC) , and uses stable IP address. In the future, with the development of IPv6 ,these customer will hope to transfer their service to IPv6,but they donot want to use IP access network(maybe they donot want to change their network sharply). In this secanrio, we think IPv6oA will be a choice to solve the problem. And upgrade a IPv4 IWF to DS IWF may be economical 

First, I owe you an apology. I was unnecessarily rough with you Friday, and that was inappropriate of me.

On Aug 7, 2012, at 6:12 AM, Maglione Roberta wrote:

> If I understand your draft correctly you are proposing a new interworking function on the Access Node, so you are basically specifying new requirements for the Access Node.
> 
> Why are you discussing this topic in IETF? Isn't this Broadband Forum's territory? BBF is the SDO that specifies requirements for Access Node and if I remember correctly this interworking function was discussed and finally not included in TR-177 some years.
> 
> If you think this work is needed, for the scenario you described, I would suggest discussing this proposal in BBF first.

That said, I agree with Maglione. Direct interworking of a virtual circuit protocol (ATM) with a LAN protocol (Ethernet) is not something the IETF has chosen to specify in the past. Reason: we have a defined interworking function between any two link layer interfaces, which one might use between interfaces of the same type for management reasons and in any event one would use between interfaces of different types. It is correct that by directly connecting the two devices, one removes the necessity of a two-port router; one does so at the cost of adding significant complexity to both the protocols, as your draft describes, and the functionality of the switch. Personally, I think you will be far better off with a router. And in any event, this is BBF territory; if the BBF wants to have IETF collusion, we can discuss that, but I think you need first to discuss it with them.