IETF Logo Mail Archive

Re: [CCAMP] Vendor-Specific Application Code in draft-ietf-ccamp-rwa-wson-encode

"Doolan, Paul (Coriant - US/Irving)" <paul.doolan@coriant.com> Wed, 28 January 2015 21:01 UTC

Return-Path: <paul.doolan@coriant.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14CB31A1AAE for <ccamp@ietfa.amsl.com>; Wed, 28 Jan 2015 13:01:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 kgsXHicPryYn for <ccamp@ietfa.amsl.com>; Wed, 28 Jan 2015 13:01:43 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0645.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::645]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BBBE1A005C for <ccamp@ietf.org>; Wed, 28 Jan 2015 13:01:42 -0800 (PST)
Received: from DB3PR04MB0761.eurprd04.prod.outlook.com (25.160.51.152) by DB3PR04MB0763.eurprd04.prod.outlook.com (25.160.51.154) with Microsoft SMTP Server (TLS) id 15.1.65.19; Wed, 28 Jan 2015 21:01:14 +0000
Received: from DB3PR04MB0761.eurprd04.prod.outlook.com ([25.160.51.152]) by DB3PR04MB0761.eurprd04.prod.outlook.com ([25.160.51.152]) with mapi id 15.01.0065.013; Wed, 28 Jan 2015 21:01:14 +0000
From: "Doolan, Paul (Coriant - US/Irving)" <paul.doolan@coriant.com>
To: Leeyoung <leeyoung@huawei.com>
Thread-Topic: [CCAMP] Vendor-Specific Application Code in draft-ietf-ccamp-rwa-wson-encode
Thread-Index: AQHQNyyAc6iYd43akkuKQTVCSlXJGZzN8F2AgAAengCAA5dgAIAEL7YAgAAd5QCAABjjAA==
Date: Wed, 28 Jan 2015 21:01:13 +0000
Message-ID: <249BEEE4-BBB1-4635-9E2A-83A7C1F15D8D@coriant.com>
References: <006901d0371a$9e1f1960$da5d4c20$@olddog.co.uk> <8DBC3FDAC14BE441AED9C5939C77758509EE3A6C@US70TWXCHMBA12.zam.alcatel-lucent.com> <BN1PR05MB0411009341243A4FCC26E64CE360@BN1PR05MB041.namprd05.prod.outlook.com> <8DBC3FDAC14BE441AED9C5939C77758509EE3B48@US70TWXCHMBA12.zam.alcatel-lucent.com> <010901d0373e$ac0d7ed0$04287c70$@olddog.co.uk> <8DBC3FDAC14BE441AED9C5939C77758509EE461F@US70TWXCHMBA12.zam.alcatel-lucent.com> <F64C10EAA68C8044B33656FA214632C83B4DF954@MISOUT7MSGUSRDE.ITServices.sbc.com> <7AEB3D6833318045B4AE71C2C87E8E1729C7F07B@dfweml706-chm>
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E1729C7F07B@dfweml706-chm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [32.210.21.102]
authentication-results: huawei.com; dkim=none (message not signed) header.d=none; huawei.com; dmarc=none action=none header.from=coriant.com;
x-dmarcaction-test: None
x-microsoft-antispam: BCL:0;PCL:0;RULEID:(3005004);SRVR:DB3PR04MB0763;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DB3PR04MB0763;
x-forefront-prvs: 047001DADA
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(377454003)(24454002)(82746002)(62966003)(46102003)(102836002)(19580395003)(54356999)(19580405001)(2656002)(76176999)(106116001)(77156002)(40100003)(2900100001)(2950100001)(122556002)(16236675004)(33656002)(92566002)(50986999)(87936001)(66066001)(83716003)(110136001)(93886004)(86362001)(36756003)(230783001)(7059030)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:DB3PR04MB0763; H:DB3PR04MB0761.eurprd04.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
Content-Type: multipart/alternative; boundary="_000_249BEEE4BBB146359E2A83A7C1F15D8Dcoriantcom_"
MIME-Version: 1.0
X-OriginatorOrg: coriant.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jan 2015 21:01:13.8682 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 76595477-907e-4695-988b-a6b39087332d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR04MB0763
Archived-At: <http://mailarchive.ietf.org/arch/msg/ccamp/TX4X75aJ8zkf6htuainD9u_GND0>
X-Mailman-Approved-At: Wed, 28 Jan 2015 13:35:44 -0800
Cc: "ccamp-chairs@tools.ietf.org" <ccamp-chairs@tools.ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "draft-ietf-ccamp-rwa-wson-encode.all@tools.ietf.org" <draft-ietf-ccamp-rwa-wson-encode.all@tools.ietf.org>
Subject: Re: [CCAMP] Vendor-Specific Application Code in draft-ietf-ccamp-rwa-wson-encode
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 28 Jan 2015 21:01:46 -0000

On Jan 28, 2015, at 2:32 PM, Leeyoung <leeyoung@huawei.com<mailto:leeyoung@huawei.com>>
 wrote:

Hi Young,

My point is how vendor specific code would be really helpful even if we employ the OUI field.

Without it there is risk of collision. A system that receives a proprietary code point it recognizes is, without the OUI, unable to tell whether that code point was generated by an equipment with the same proprietary implementation or by some other system that just happened to pick the same code.

pd

v2.23.0 | Report a Bug | By Email