[Capwap] WG, Please confirm whether RFC5415 support IPv4z and IPv6z
young <young@h3c.com> Tue, 26 January 2010 07:17 UTC
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B17CA3A6818 for <ietfarch-capwap-archive@core3.amsl.com>; Mon, 25 Jan 2010 23:17:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.69
X-Spam-Level:
X-Spam-Status: No, score=-0.69 tagged_above=-999 required=5 tests=[AWL=2.309, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_LOW=-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 kZw1wAf2AAlJ for <ietfarch-capwap-archive@core3.amsl.com>; Mon, 25 Jan 2010 23:17:36 -0800 (PST)
Received: from lists.tigertech.net (lists.tigertech.net [64.62.209.34]) by core3.amsl.com (Postfix) with ESMTP id 0E08E3A6810 for <capwap-archive@lists.ietf.org>; Mon, 25 Jan 2010 23:17:36 -0800 (PST)
Received: from zoidberg.tigertech.net (localhost [127.0.0.1]) by zoidberg.tigertech.net (Postfix) with ESMTP id 59C9DE181CC for <capwap-archive@lists.ietf.org>; Mon, 25 Jan 2010 23:17:45 -0800 (PST)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31]) by lists.tigertech.net (Postfix) with ESMTP id 7A2DAE240E1 for <capwap@lists.tigertech.net>; Mon, 25 Jan 2010 23:17:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx1.tigertech.net (Postfix) with ESMTP id 698EF3610002 for <capwap@frascone.com>; Mon, 25 Jan 2010 23:17:39 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from mx1.tigertech.net (localhost [127.0.0.1]) by mx1.tigertech.net (Postfix) with ESMTP id 94A373610001 for <capwap@frascone.com>; Mon, 25 Jan 2010 23:17:38 -0800 (PST)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (High) (P0); Whitelisted TTSSA (young@h3c.com whitelisted)
Received: from huawei-3com.com (unknown [60.191.123.56]) by mx1.tigertech.net (Postfix) with ESMTP for <capwap@frascone.com>; Mon, 25 Jan 2010 23:17:38 -0800 (PST)
Received: from huawei-3com.com (localhost [127.0.0.1]) by h3cml02-in.huawei-3com.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0KWU00E3ZFHR5R@h3cml02-in.huawei-3com.com> for capwap@frascone.com; Tue, 26 Jan 2010 15:29:51 +0800 (CST)
Received: from h3cmta02-ds.h3c.com ([172.25.12.70]) by h3cml02-in.huawei-3com.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0KWU00I8DFHR2C@h3cml02-in.huawei-3com.com> for capwap@frascone.com; Tue, 26 Jan 2010 15:29:51 +0800 (CST)
Received: from smtp1.h3c.com ([172.25.14.252]) by h3cmta02-ds.h3c.com (Lotus Domino Release 8.5FP1) with ESMTP id 2010012615173556-1839839 ; Tue, 26 Jan 2010 15:17:35 +0800
Received: from unknown (HELO s00338) ([10.154.68.122]) by smtp1.h3c.com with ESMTP; Tue, 26 Jan 2010 15:14:27 +0800
Date: Tue, 26 Jan 2010 15:17:26 +0800
From: young <young@h3c.com>
To: capwap@frascone.com
Message-id: <006f01ca9e57$9d806060$7a449a0a@h3c.huawei3com.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook, Build 10.0.6856
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-MIMETrack: Itemize by SMTP Server on h3cmta02-ds/h3c(Release 8.5FP1|June 15, 2009) at 2010-01-26 15:17:35, Serialize by Router on h3cmta02-ds/h3c(Release 8.5FP1|June 15, 2009) at 2010-01-26 15:17:35, Serialize complete at 2010-01-26 15:17:35
Thread-index: AcqeV50JW0OiVx4YSf+owdadXf+Q4A==
Cc: pasi.eronen@nokia.com, Yong Zhang <yozhang@gmail.com>
Subject: [Capwap] WG, Please confirm whether RFC5415 support IPv4z and IPv6z
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Post: <mailto:capwap@frascone.com>
X-Tigertech-Mailman-Hint: 636170776170
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>, <mailto:capwap-request@frascone.com?subject=subscribe>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>, <mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com
Hi, all: Kindly do some favour and confirm whether CAPWAP protocol (RFC5415) Supports IPv4z and IPv6z? I give some info here from the perspective of MIB related RFCs. When a MIB defines an Address type object (for example, WTP's address), it requires to point out its address type (v4, v6 and so on) RFC4001 already defined TC (InetAddressType) for IP address type, also give the value list: SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4), dns(16) } When a MIB object is defined with TC InetAddressType, it should specify Which IP address type (ipv4, or so on) it exactly support. MY question is: Whether CAPWAP supports the ipv4z and ipv6z? Please also refer to Pasi's comments to the MIB draft: //////////// capwapBaseWtpProfileWtpStaticIpType: How would the "ipv4z" type be used by the CAPWAP protocol? (it doesn't seem to use the zone index in any way) Could you give some guidance? I appreciate your help. Regards Richard The related content in the RFC4001: InetAddressType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In Daniele, et al. Standards Track PAGE 6 ---------------------------------------------------------------------------- ---- RFC 4001 Internet Network Address Conventions February 2005 particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1))." SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4), dns(16) } InetAddressIPv4z ::= TEXTUAL-CONVENTION DISPLAY-HINT "1d.1d.1d.1d%4d" STATUS current DESCRIPTION "Represents a non-global IPv4 network address, together with its zone index: Octets Contents Encoding 1-4 IPv4 address network-byte order 5-8 zone index network-byte order The corresponding InetAddressType value is ipv4z(3). The zone index (bytes 5-8) is used to disambiguate identical address values on nodes that have interfaces attached to different zones of the same scope. The zone index may contain the special value 0, which refers to the default zone for each scope. This textual convention SHOULD NOT be used directly in object Daniele, et al. Standards Track PAGE 8 ---------------------------------------------------------------------------- ---- RFC 4001 Internet Network Address Conventions February 2005 definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair." SYNTAX OCTET STRING (SIZE (8)) InetAddressIPv6z ::= TEXTUAL-CONVENTION DISPLAY-HINT "2x:2x:2x:2x:2x:2x:2x:2x%4d" STATUS current DESCRIPTION "Represents a non-global IPv6 network address, together with its zone index: Octets Contents Encoding 1-16 IPv6 address network-byte order 17-20 zone index network-byte order The corresponding InetAddressType value is ipv6z(4). The zone index (bytes 17-20) is used to disambiguate identical address values on nodes that have interfaces attached to different zones of the same scope. The zone index may contain the special value 0, which refers to the default zone for each scope. This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair." SYNTAX OCTET STRING (SIZE (20)) Regards Richard _________________________________________________________________ To unsubscribe or modify your subscription options, please visit: http://lists.frascone.com/mailman/listinfo/capwap Archives: http://lists.frascone.com/pipermail/capwap