Re: [CCAMP] radio-link and carrier-termination iana interface types

"Yemin (Amy)" <amy.yemin@huawei.com> Thu, 08 November 2018 16:08 UTC

Return-Path: <amy.yemin@huawei.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4422128BCC for <ccamp@ietfa.amsl.com>; Thu, 8 Nov 2018 08:08:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eacejX9G2Pu9 for <ccamp@ietfa.amsl.com>; Thu, 8 Nov 2018 08:08:56 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B159A1286E7 for <ccamp@ietf.org>; Thu, 8 Nov 2018 08:08:56 -0800 (PST)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 7658164A6BCF3; Thu, 8 Nov 2018 16:08:51 +0000 (GMT)
Received: from DGGEMM421-HUB.china.huawei.com (10.1.198.38) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 8 Nov 2018 16:08:53 +0000
Received: from DGGEMM528-MBX.china.huawei.com ([169.254.8.232]) by dggemm421-hub.china.huawei.com ([10.1.198.38]) with mapi id 14.03.0415.000; Fri, 9 Nov 2018 00:08:50 +0800
From: "Yemin (Amy)" <amy.yemin@huawei.com>
To: tom petch <ietfc@btconnect.com>, Kallimanis Theodoros <tks@intracom-telecom.com>, "ccamp@ietf.org" <ccamp@ietf.org>, "jonas.ahlberg@ericsson.com" <jonas.ahlberg@ericsson.com>, "Xi.Li@neclab.eu" <Xi.Li@neclab.eu>, "daniela.spreafico@nokia.com" <daniela.spreafico@nokia.com>, "Marko.Vaupotic@avianet.com" <Marko.Vaupotic@avianet.com>
Thread-Topic: [CCAMP] radio-link and carrier-termination iana interface types
Thread-Index: AdRw+z2vcl42f5ytSjSPIq+FPSqYEAGXxbk6
Date: Thu, 08 Nov 2018 16:08:49 +0000
Message-ID: <9C5FD3EFA72E1740A3D41BADDE0B461FCFA7B460@DGGEMM528-MBX.china.huawei.com>
References: <3bea4c321040be4d9454361fee3158dc@iris>, <061001d471e4$171dd420$4001a8c0@gateway.2wire.net> <9C5FD3EFA72E1740A3D41BADDE0B461FCFA78C38@DGGEMM528-MBX.china.huawei.com>, <022001d476b8$12629e60$4001a8c0@gateway.2wire.net>
In-Reply-To: <022001d476b8$12629e60$4001a8c0@gateway.2wire.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.126.175.181]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/EPGAcsWgtacDFGkQGrmjzJ0lTWk>
Subject: Re: [CCAMP] radio-link and carrier-termination iana interface types
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2018 16:09:00 -0000

Hi Tom and Theodoros,

Thanks for the discussion.
In the current draft the type defintion for radio-link-terminal and carrier-termination is under ietf-microwave-types model. But it should be better to add them to IANA-ifType registry.
Today we talked with the IANA delegates, it's suggested to add the request in the IANA section of the draft. 
Whether the MIB type registry is created will be decided by the IANA. From this draft, it's not necessary to ask for MIB  registry. However the MIB registry may be automaticlly created when creating the ifType registry. 
Another draft updated will be provided soon. 

BR,
Amy
________________________________________
发件人: tom petch [ietfc@btconnect.com]
发送时间: 2018年11月8日 0:38
收件人: Yemin (Amy); Kallimanis Theodoros; ccamp@ietf.org; jonas.ahlberg@ericsson.com; Xi.Li@neclab.eu; daniela.spreafico@nokia.com; Marko.Vaupotic@avianet.com
主题: Re: [CCAMP] radio-link and carrier-termination iana interface types

----- Original Message -----
From: "Yemin (Amy)" <amy.yemin@huawei.com>
Sent: Wednesday, November 07, 2018 8:00 AM

> Hi Theodoros,
>
> I discussed with serveral people at the IETF week, the answer is the
same as Tom gave.
> We cannot use a YANG model to ask for IANA registry for MIB.

Amy

That is not right.  A request is made to IANA in the IANA Considerations
for a new interface type, they pass it to the Designated Expert.  If the
request is granted, then the YANG Interface Type module and the SMI
Interface Type module are updated.  Easy peasy.

The request needs to reference a suitable technical defintion in a
stable source as judged by the Designated Expert.  RFC, ITU-T
Recommendations qualify; web pages generally do not (although one of the
W3C should:-)

Tom Petch





> As YANG is normally used by NETCONF/RESTCONF, MIB is used by SNMP.
> If there's interest on MIB, another draft should be sumbitted and ask
for the registry.
>
> BR,
> Amy
> ________________________________________
> 发件人: tom petch [ietfc@btconnect.com]
> 发送时间: 2018年11月1日 21:10
> 收件人: Kallimanis Theodoros; ccamp@ietf.org;
jonas.ahlberg@ericsson.com; Yemin (Amy); Xi.Li@neclab.eu;
daniela.spreafico@nokia.com; Marko.Vaupotic@avianet.com
> 主题: Re: [CCAMP] radio-link and carrier-termination iana interface
types
>
> ---- Original Message -----
> From: "Kallimanis Theodoros" <tks@intracom-telecom.com>
> To: <ccamp@ietf.org>; <jonas.ahlberg@ericsson.com>;
> <amy.yemin@huawei.com>; <Xi.Li@neclab.eu>;
> <daniela.spreafico@nokia.com>; <Marko.Vaupotic@avianet.com>
> Sent: Wednesday, October 31, 2018 10:27 AM
>
> Hello
>
> I would like to ask a question regarding to ietf-microwave-types
module.
>
> For radio-link-terminal and carrier-termination, is it expected that
> these new interface-types will be also registered at IANA Interface
Type
> registry for  IANAifType-MIB?
>
> <tp>
>
> The strict answer is no, they will not be added to the registry.  They
> are only added when the IANA Cosiderations asks IANA to do so and this
> I-D makes no such request.
>
> If such a request were made, then they would be added both to the
> IANA-maintained MIB Module and to the IANA-maintained YANG  module.
>
> I did think of this a year ago and thought them too specific to CCAMP,
> worth putting into a YANG module but not inflicting them on the IETF
at
> large, but do not think this ever got discussed on the WG list.
>
> Tom Petch
>
>
> BEST REGARDS
>
> Theodoros Kallimanis
> Principal Engineer (Systems & SW)
>
> Department SSD
> ______________________________________
> Intracom Telecom
> 19.7 km Markopoulou Ave., Peania, GR 19002
>
> Building A3, 2nd floor
> t:   +30 2106671961
> f:   +30 2106671446
> m: +30 6941636679
>  <mailto:tks@intracom-telecom.com> tks@intracom-telecom.com
>  <http://www.intracom-telecom.com/> www.intracom-telecom.com
>
>
>
>
>
>
>
>
> ----------------------------------------------------------------------
--
> --------
>
>
> > _______________________________________________
> > CCAMP mailing list
> > CCAMP@ietf.org
> > https://www.ietf.org/mailman/listinfo/ccamp
> >
>
>