Re: [ANCP] Question about the Tech Type in draft-ietf-ancp-protocol-05
Fortune HUANG <fqhuang@huawei.com> Mon, 13 April 2009 01:16 UTC
Return-Path: <fqhuang@huawei.com>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 758353A6C7E for <ancp@core3.amsl.com>; Sun, 12 Apr 2009 18:16:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.667
X-Spam-Level: *
X-Spam-Status: No, score=1.667 tagged_above=-999 required=5 tests=[AWL=-0.582, BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
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 1G0rOjIVuapD for <ancp@core3.amsl.com>; Sun, 12 Apr 2009 18:16:12 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 8D4663A6934 for <ancp@ietf.org>; Sun, 12 Apr 2009 18:16:11 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KI000HVBM8M56@szxga02-in.huawei.com> for ancp@ietf.org; Mon, 13 Apr 2009 09:17:11 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KI000I9IM8MC0@szxga02-in.huawei.com> for ancp@ietf.org; Mon, 13 Apr 2009 09:17:10 +0800 (CST)
Received: from h36145c ([10.70.39.123]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KI000JB7M8M2R@szxml06-in.huawei.com> for ancp@ietf.org; Mon, 13 Apr 2009 09:17:10 +0800 (CST)
Date: Mon, 13 Apr 2009 09:17:10 +0800
From: Fortune HUANG <fqhuang@huawei.com>
In-reply-to: <9BD5D7887235424FA97DFC223CAE3C281BE875A2@proton.jnpr.net>
To: 'Sanjay Wadhwa' <swadhwa@juniper.net>, ancp@ietf.org
Message-id: <003c01c9bbd5$91cd9f90$7b27460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_muSfNXPKajumAO2GhwaTlA)"
Thread-index: Acm3OSz0fRJk81LAS/ytLoiulpiBygCsVGqQAHpyZPA=
Subject: Re: [ANCP] Question about the Tech Type in draft-ietf-ancp-protocol-05
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2009 01:16:14 -0000
Hi Sanjay, Thank you very much for your answer. But in the text in section 5.4.1.1 as follows, if the tech type is new registry, then what types of technologies are the 0x01 ~ 0x04 indicates respectively? I think they should be clearly specified, although I guess they might be 0x01 for 802.3, 0x02 for 802.11a/b/g, 0x03 for 802.163, 0x04 for 802.16m. Is it correct? "Tech Type An 8-bit field indicating the applicable technology type value. The Message Type plus the Tech Value uniquely define a single Extension Type and can be treated as a single 16 bit extension type. "Tech Type" value of 0x05 SHOULD be used by ANCP for DSL technology. 0x00 Extension block not in use. 0x01 - 0x04 Already in use by various technologies 0x05 DSL 0x06 - 0xFE Reserved 0xFF Base Specification Use " Best Regards, Fortune _____ From: Sanjay Wadhwa [mailto:swadhwa@juniper.net] Sent: Friday, April 10, 2009 10:47 PM To: Fortune HUANG; ancp@ietf.org Subject: RE: [ANCP] Question about the Tech Type in draft-ietf-ancp-protocol-05 Hi Fortune The intent is to define an ANCP specific tech-type registry, and not take what MIP/PMIP uses as per your reference below. Regards -Sanjay _____ From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Fortune HUANG Sent: Tuesday, April 07, 2009 12:28 AM To: ancp@ietf.org Subject: [ANCP] Question about the Tech Type in draft-ietf-ancp-protocol-05 Hi all, I have a question about the Tech Type in ANCP protocol for clarification. It says "Tech Type" value of 0x05 SHOULD be used by ANCP for DSL technology in section 5.4.1.1 of draft-ietf-ancp-protocol-05. I can find two related technology type registries at the website http://www.iana.org/protocols/ as follows, but the 0x05 has been allocated in both registries. Is the first registry with the name Access Technology Types the right registry for the Tech Type in ANCP protocol, please? If it is, I propose we change the 0x05 for DSL in section 5.4.1.1 to be 0x09 or "to be allocated by IANA" in order to avoid incorrect implementation. Registry Name: Access Technology Types Reference: [RFC-leung-mip4-proxy-mode-10.txt] Registration Procedures: Expert Review Registry: Value Name Reference -------- ------------------------------------------------- --------- 0 Reserved [RFC-leung-mip4-proxy-mode-10.txt] 1 802.3 [RFC-leung-mip4-proxy-mode-10.txt] 2 802.11a/b/g [RFC-leung-mip4-proxy-mode-10.txt] 3 802.16e [RFC-leung-mip4-proxy-mode-10.txt] 4 802.16m [RFC-leung-mip4-proxy-mode-10.txt] 5 3GPP EUTRAN/LTE [RFC-leung-mip4-proxy-mode-10.txt] 6 3GPP UTRAN/GERAN [RFC-leung-mip4-proxy-mode-10.txt] 7 3GPP2 1xRTT/HRPD [RFC-leung-mip4-proxy-mode-10.txt] 8 3GPP2 UMB [RFC-leung-mip4-proxy-mode-10.txt] 9-255 Unassigned Access Technology Type Option type values Reference [ <http://www.iana.org/go/rfc5213> RFC5213] Registration Procedures Expert Review Value Description Reference Registration Date 0 Reserved [ <http://www.iana.org/go/rfc5213> RFC5213] 1 Virtual [ <http://www.iana.org/go/rfc5213> RFC5213] 2 PPP [ <http://www.iana.org/go/rfc5213> RFC5213] 3 IEEE 802.3 [ <http://www.iana.org/go/rfc5213> RFC5213] 4 IEEE 802.11a/b/g [ <http://www.iana.org/go/rfc5213> RFC5213] 5 IEEE 802.16e [ <http://www.iana.org/go/rfc5213> RFC5213] 6 3GPP GERAN [ <http://www.3gpp.org/specs/specs.htm> 3GPP TS 29.275][ <http://www.iana.org/assignments/mobility-parameters/mobility-parameters.xht ml#Julien_Laganier> Julien_Laganier] 2008-07-30 7 3GPP UTRAN [ <http://www.3gpp.org/specs/specs.htm> 3GPP TS 29.275][ <http://www.iana.org/assignments/mobility-parameters/mobility-parameters.xht ml#Julien_Laganier> Julien_Laganier] 2008-07-30 8 3GPP E-UTRAN [ <http://www.3gpp.org/specs/specs.htm> 3GPP TS 29.275][ <http://www.iana.org/assignments/mobility-parameters/mobility-parameters.xht ml#Julien_Laganier> Julien_Laganier] 2008-07-30 9 3GPP2 eHRPD [ <http://www.3gpp2.org/public_html/specs/index.cfm> 3GPP2 X.P0057][ <http://www.iana.org/assignments/mobility-parameters/mobility-parameters.xht ml#Kuntal_Chowdhury> Kuntal_Chowdhury] 2008-08-21 10 3GPP2 HRPD [ <http://www.3gpp2.org/public_html/specs/index.cfm> 3GPP2 X.P0061][ <http://www.iana.org/assignments/mobility-parameters/mobility-parameters.xht ml#Kuntal_Chowdhury> Kuntal_Chowdhury] 2008-08-21 11 3GPP2 1xRTT [ <http://www.3gpp2.org/public_html/specs/index.cfm> 3GPP2 X.S0011][ <http://www.iana.org/assignments/mobility-parameters/mobility-parameters.xht ml#Kuntal_Chowdhury> Kuntal_Chowdhury] 2008-08-21 12 3GPP2 UMB [ <http://www.3gpp2.org/public_html/specs/index.cfm> 3GPP2 X.S0054][ <http://www.iana.org/assignments/mobility-parameters/mobility-parameters.xht ml#Kuntal_Chowdhury> Kuntal_Chowdhury] 2008-08-21 13-255 Unassigned Best Regards, Fortune
- [ANCP] Question about the Tech Type in draft-ietf… Fortune HUANG
- Re: [ANCP] Question about the Tech Type in draft-… Sanjay Wadhwa
- Re: [ANCP] Question about the Tech Type in draft-… Fortune HUANG
- Re: [ANCP] Question about the Tech Type in draft-… Fortune HUANG
- Re: [ANCP] Question about the Tech Type in draft-… Sanjay Wadhwa
- Re: [ANCP] Question about the TechType in draft-i… HaagT
- Re: [ANCP] Question about the Tech Type in draft-… Fortune HUANG