IETF Logo Mail Archive

Re: [ANCP] Question about the Tech Type in draft-ietf-ancp-protocol-05

Sanjay Wadhwa <swadhwa@juniper.net> Fri, 10 April 2009 14:52 UTC

Return-Path: <swadhwa@juniper.net>
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 F1E7E3A67DD for <ancp@core3.amsl.com>; Fri, 10 Apr 2009 07:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.765
X-Spam-Level:
X-Spam-Status: No, score=-5.765 tagged_above=-999 required=5 tests=[AWL=0.833, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 YvC8J9Q2Cn0v for <ancp@core3.amsl.com>; Fri, 10 Apr 2009 07:52:07 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by core3.amsl.com (Postfix) with ESMTP id 1C2723A6925 for <ancp@ietf.org>; Fri, 10 Apr 2009 07:52:06 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKSd9dUvpfvIwwR3IZ6GnbIPn+7pfUE7s3@postini.com; Fri, 10 Apr 2009 07:53:16 PDT
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.340.0; Fri, 10 Apr 2009 07:47:05 -0700
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 10 Apr 2009 07:47:05 -0700
Received: from antipi.jnpr.net ([10.10.2.34]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 10 Apr 2009 07:47:05 -0700
Received: from proton.jnpr.net ([10.10.2.37]) by antipi.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Fri, 10 Apr 2009 10:47:03 -0400
x-mimeole: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9B9EB.34E9B52C"
Date: Fri, 10 Apr 2009 10:47:00 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C281BE875A2@proton.jnpr.net>
In-Reply-To: <00d701c9b739$2d0c4ed0$7b27460a@china.huawei.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [ANCP] Question about the Tech Type in draft-ietf-ancp-protocol-05
Thread-Index: Acm3OSz0fRJk81LAS/ytLoiulpiBygCsVGqQ
References: <00d701c9b739$2d0c4ed0$7b27460a@china.huawei.com>
From: Sanjay Wadhwa <swadhwa@juniper.net>
To: Fortune HUANG <fqhuang@huawei.com>, ancp@ietf.org
X-OriginalArrivalTime: 10 Apr 2009 14:47:03.0799 (UTC) FILETIME=[3667B870:01C9B9EB]
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: Fri, 10 Apr 2009 14:52:09 -0000

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 

[RFC5213 <http://www.iana.org/go/rfc5213> ] 

Registration Procedures 

Expert Review 

Value

Description

Reference

Registration Date

0

Reserved

[RFC5213 <http://www.iana.org/go/rfc5213> ]

 

1

Virtual

[RFC5213 <http://www.iana.org/go/rfc5213> ]

 

2

PPP

[RFC5213 <http://www.iana.org/go/rfc5213> ]

 

3

IEEE 802.3

[RFC5213 <http://www.iana.org/go/rfc5213> ]

 

4

IEEE 802.11a/b/g

[RFC5213 <http://www.iana.org/go/rfc5213> ]

 

5

IEEE 802.16e

[RFC5213 <http://www.iana.org/go/rfc5213> ]

 

6

3GPP GERAN

[3GPP TS 29.275 <http://www.3gpp.org/specs/specs.htm> ][Julien_Laganier
<http://www.iana.org/assignments/mobility-parameters/mobility-parameters
.xhtml#Julien_Laganier> ]

2008-07-30

7

3GPP UTRAN

[3GPP TS 29.275 <http://www.3gpp.org/specs/specs.htm> ][Julien_Laganier
<http://www.iana.org/assignments/mobility-parameters/mobility-parameters
.xhtml#Julien_Laganier> ]

2008-07-30

8

3GPP E-UTRAN

[3GPP TS 29.275 <http://www.3gpp.org/specs/specs.htm> ][Julien_Laganier
<http://www.iana.org/assignments/mobility-parameters/mobility-parameters
.xhtml#Julien_Laganier> ]

2008-07-30

9

3GPP2 eHRPD

[3GPP2 X.P0057 <http://www.3gpp2.org/public_html/specs/index.cfm>
][Kuntal_Chowdhury
<http://www.iana.org/assignments/mobility-parameters/mobility-parameters
.xhtml#Kuntal_Chowdhury> ]

2008-08-21

10

3GPP2 HRPD

[3GPP2 X.P0061 <http://www.3gpp2.org/public_html/specs/index.cfm>
][Kuntal_Chowdhury
<http://www.iana.org/assignments/mobility-parameters/mobility-parameters
.xhtml#Kuntal_Chowdhury> ]

2008-08-21

11

3GPP2 1xRTT

[3GPP2 X.S0011 <http://www.3gpp2.org/public_html/specs/index.cfm>
][Kuntal_Chowdhury
<http://www.iana.org/assignments/mobility-parameters/mobility-parameters
.xhtml#Kuntal_Chowdhury> ]

2008-08-21

12

3GPP2 UMB

[3GPP2 X.S0054 <http://www.3gpp2.org/public_html/specs/index.cfm>
][Kuntal_Chowdhury
<http://www.iana.org/assignments/mobility-parameters/mobility-parameters
.xhtml#Kuntal_Chowdhury> ]

2008-08-21

13-255

Unassigned

 

 

 

 

Best Regards,

Fortune

v2.23.0 | Report a Bug | By Email