RE: URN Namespace for MEF

"Ranganathan, Raghu" <rraghu@ciena.com> Mon, 19 October 2015 22:49 UTC

Return-Path: <prvs=1734f4d549=rraghu@ciena.com>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 151711B2E1C for <urn-nid@ietfa.amsl.com>; Mon, 19 Oct 2015 15:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.266
X-Spam-Level:
X-Spam-Status: No, score=-4.266 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, 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 lKtk0EzVNXCr for <urn-nid@ietfa.amsl.com>; Mon, 19 Oct 2015 15:49:42 -0700 (PDT)
Received: from mx0a-00103a01.pphosted.com (mx0a-00103a01.pphosted.com [67.231.144.234]) (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 91CEB1B2DBC for <urn-nid@apps.ietf.org>; Mon, 19 Oct 2015 15:49:29 -0700 (PDT)
Received: from pps.filterd (m0000419.ppops.net [127.0.0.1]) by mx0a-00103a01.pphosted.com (8.15.0.59/8.15.0.59) with SMTP id t9JMml7G006208; Mon, 19 Oct 2015 18:49:29 -0400
Received: from vawvcgsie2k1302.ciena.com (lin1-118-36-36.ciena.com [63.118.36.36]) by mx0a-00103a01.pphosted.com with ESMTP id 1xkj12ytrg-1 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 19 Oct 2015 18:49:29 -0400
Received: from MDWEXCHCGSIHT01.ciena.com (10.4.140.106) by VAWVCGSIE2K1302.ciena.com (10.4.62.16) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 19 Oct 2015 18:49:27 -0400
Received: from ONWVEXCHHT02.ciena.com (10.128.6.17) by MDWEXCHCGSIHT01.ciena.com (10.4.140.106) with Microsoft SMTP Server (TLS) id 8.3.389.2; Mon, 19 Oct 2015 18:49:26 -0400
Received: from ONWVEXCHMB03.ciena.com ([::1]) by ONWVEXCHHT02.ciena.com ([::1]) with mapi; Mon, 19 Oct 2015 18:49:26 -0400
From: "Ranganathan, Raghu" <rraghu@ciena.com>
To: "bclaise@cisco.com" <bclaise@cisco.com>, "mjethanandani@gmail.com" <mjethanandani@gmail.com>, "urn-nid@apps.ietf.org" <urn-nid@apps.ietf.org>, "duerst@it.aoyama.ac.jp" <duerst@it.aoyama.ac.jp>
Date: Mon, 19 Oct 2015 18:49:25 -0400
Subject: RE: URN Namespace for MEF
Thread-Topic: URN Namespace for MEF
Thread-Index: AdEKu16dAUl/PcWUT9SfZn3blrYUmQABQi+7
Message-ID: <679E55ADEABC9443947F5AD6F3ED464A21AF849AD5@ONWVEXCHMB03.ciena.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_679E55ADEABC9443947F5AD6F3ED464A21AF849AD5ONWVEXCHMB03c_"
MIME-Version: 1.0
X-TM-AS-Product-Ver: SMEX-11.0.0.4179-8.000.1202-21888.004
X-TM-AS-Result: No--24.898400-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2015-10-20_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1507310000 definitions=main-1510190398
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/uhetQyMQLthKs7aXAdGWaNXMZdg>
Cc: "jason.wolfe@bell.ca" <jason.wolfe@bell.ca>
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn-nid/>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2015 22:49:48 -0000

With MEF, we kept struggling with "metro" (for M) given that Operators are selling services that span nations and continents.

(Good one on "Simple"!! ).

--Raghu
Sent from my phone

-----Original Message-----
From: Martin J. Dürst [duerst@it.aoyama.ac.jp]
Received: Monday, 19 Oct 2015, 5:13PM
To: Ranganathan, Raghu [rraghu@ciena.com]; bclaise@cisco.com [bclaise@cisco.com]; mjethanandani@gmail.com [mjethanandani@gmail.com]; urn-nid@apps.ietf.org [urn-nid@apps.ietf.org]
CC: jason.wolfe@bell.ca [jason.wolfe@bell.ca]
Subject: Re: URN Namespace for MEF

On 2015/10/19 21:01, Ranganathan, Raghu wrote:
> One of your suggestions is probably helpful I think, i.e., reference to the website (mef.net).

Then please use it, thanks.

What I care about isn't publicity language (like below), but an easy way
for readers to nail down what organization they are dealing with.
"mef.net" covers that. It would also be helpful to know what the forum
is about (the words "carrier ethernet" should be sufficient), and to get
a hint at how to remember "MEF" ("Metropolitan Ethernet Forum" is the
best explanation I can come up, although that seems to be taboo).

Regards,   Martin.

P.S.: When I was on the W3C team, W3C had a similar case: SOAP. That
initially stood for "Simple Object Access Protocol", but later it was
decided that it would be just "SOAP". It was too complicated to sell it
as "simple".


> -----Original Message-----
> From: Ranganathan, Raghu
> Sent: Monday, October 19, 2015 6:41 AM
> To: 'Martin J. Dürst'; bclaise@cisco.com; mjethanandani@gmail.com; urn-nid@apps.ietf.org
> Cc: jason.wolfe@bell.ca
> Subject: RE: URN Namespace for MEF
>
> Hello Martin
> Introduction has in 1st para as follows:
> "The MEF Forum (MEF), is a nonprofit international industry standards
>     organization, dedicated to the worldwide adoption of Carrier Ethernet
>     (CE) networks and services.  The forum creates specifications in the
>     area of Services, Architecture, Operations and Management."
>
> Is the text in Intro sufficient? I am not sure why it is necessary to refer to whatever an organization was previously known as except for some historical Wikipedia write up. If that is critical then we can update.
> --Raghu
>
>
> -----Original Message-----
> From: Martin J. Dürst [mailto:duerst@it.aoyama.ac.jp]
> Sent: Monday, October 19, 2015 3:09 AM
> To: Ranganathan, Raghu; bclaise@cisco.com; mjethanandani@gmail.com; urn-nid@apps.ietf.org
> Cc: jason.wolfe@bell.ca
> Subject: Re: URN Namespace for MEF
>
> On 2015/10/16 19:01, Ranganathan, Raghu wrote:
>> Would "draft" be referring to draft for MANN doc?
>>
>> Regarding "MEF Forum", there is no expansion for MEF (after a recent change in name).
>
> Instead of having the three letters "MEF" appear in the abstract four times, without any clue about what that's referring to, it would be extremely helpful to outsiders (and for URN namespace registration, essentially everybody is an outsider) if there were some text such as "MEF (mef.org)" or "MEF (formerly Ethernet in the First Mile Alliance)"
> or "MEF (formerly Metro Ethernet Forum)" or whatever appropriate.
>
> Regards,   Martin.
>
>
>> --Raghu
>> Sent from my phone
>>
>> -----Original Message-----
>> From: Martin J. Dürst [duerst@it.aoyama.ac.jp]
>> Received: Friday, 16 Oct 2015, 4:52AM
>> To: Benoit Claise [bclaise@cisco.com]; Mahesh Jethanandani
>> [mjethanandani@gmail.com]; urn-nid@apps.ietf.org
>> [urn-nid@apps.ietf.org]
>> CC: Wolfe, Jason (P020296) [jason.wolfe@bell.ca]; Ranganathan, Raghu
>> [rraghu@ciena.com]
>> Subject: Re: URN Namespace for MEF
>>
>> On 2015/10/16 18:32, Benoit Claise wrote:
>>> Mahesh,
>>>
>>> I believe that you should submit the draft.
>>
>> Yes, please. Also, it would be good to give an expansion of "MEF".
>> Somewhere, something like "MEF" = "MEF Forum" turns up, but that still
>> doesn't say anything to an outsider.
>>
>> Regards,   Martin.
>>
>>> Regards, Benoit
>>>> This submission is for a URN NID for MEF. Comments are welcome on
>>>> this draft.
>>>>
>>>> There is a companion document, called the MEF Assignment of Names
>>>> and Numbers (MANN) that is an MEF document under discussion, and has
>>>> some of the answers in this template. The attached drafts points to
>>>> the MANN document in the relevant section. MANN will be posted on
>>>> MEF website once the committee has had a chance to review and approve it.
>>>>
>>>> Mahesh Jethanandani
>>>> mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>