Re: [mif] New draft about MIF API extension for combining IEEE 802.21

"Fei Song" <fsong@bjtu.edu.cn> Fri, 04 July 2014 02:01 UTC

Return-Path: <fsong@bjtu.edu.cn>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A8471A045D for <mif@ietfa.amsl.com>; Thu, 3 Jul 2014 19:01:01 -0700 (PDT)
X-Quarantine-ID: <d4slqlI95vUZ>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: -1.54
X-Spam-Level:
X-Spam-Status: No, score=-1.54 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MSGID_FROM_MTA_HEADER=0.001, RCVD_DOUBLE_IP_LOOSE=1.012, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 d4slqlI95vUZ for <mif@ietfa.amsl.com>; Thu, 3 Jul 2014 19:00:58 -0700 (PDT)
Received: from bjtu.edu.cn (mail.bjtu.edu.cn [218.249.29.198]) by ietfa.amsl.com (Postfix) with SMTP id 453B01A0240 for <mif@ietf.org>; Thu, 3 Jul 2014 19:00:58 -0700 (PDT)
X-EYOU-SPAMVALUE: 0
X-EMDG-ORIGINAL-FROM: <fsong@bjtu.edu.cn>
X-EMDG-ORIGINAL-TO: <mif@ietf.org>
X-EMDG-ORIGINAL-IP: 211.71.74.136
X-EMDG-VER: 4.1.0
Received: (eyou anti_spam gateway 4.1.0); Fri, 04 Jul 2014 09:54:09 +0800
Message-ID: <604438849.27963@bjtu.edu.cn>
X-EMDG-SMTPAUTH: fsong@bjtu.edu.cn
Received: from 211.71.74.136 by 218.249.29.198 with SMTP; Fri, 04 Jul 2014 09:54:09 +0800
Date: Fri, 04 Jul 2014 10:00:55 +0800
From: Fei Song <fsong@bjtu.edu.cn>
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <604109602.03243@bjtu.edu.cn> <604363291.17829@bjtu.edu.cn>, <604393476.05609@bjtu.edu.cn>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.91[cn]
Mime-Version: 1.0
Message-ID: <201407041000553868544@bjtu.edu.cn>
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
Archived-At: http://mailarchive.ietf.org/arch/msg/mif/0BJldUKpv-lLI2z4Fci8iFAGE-Q
Cc: mrw <mrw@lilacglade.org>, denghui02 <denghui02@hotmail.com>, mif <mif@ietf.org>
Subject: Re: [mif] New draft about MIF API extension for combining IEEE 802.21
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: fsong <fsong@bjtu.edu.cn>
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif/>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jul 2014 02:01:01 -0000

Dear Mikael:

Thanks for your reply.
If you search "802.21 part 21" in google.com or baidu.com, you would find many links for viewing the protocols (cannot download). The IEEE is not the only source.

--------------
Fei Song
>On Thu, 3 Jul 2014, Fei Song wrote:
>
>> Dear all:
>>
>> We have submitted a new draft about MIF API extension for combining IEEE 802.21.
>> http://www.ietf.org/id/draft-zhang-mif-api-extension-802-21-00.txt
>> Comments and suggestions are more than welcome.
>> Thank you very much!
>
>I intended to read up on 802.21, but you need to be an IEEE member to 
>access the linked document in the draft. I see the same private document 
>referenced from 
>http://tools.ietf.org/html/draft-zuniga-mif-802-21-overview-00#ref-IEEE802.21
>
>Is there anything we can do about this? Referencing non-public documents 
>is kind of meaningless to the general public.
>
>I at least can't say if your document makes sense because I have no way to 
>get information to understand 802.21. 
>http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_12-2/122_ieee.html 
>seems to give some background, but it's not a complete document and not 
>something that could be referred to in an RFC either.
>
>-- 
>Mikael Abrahamsson    email: swmike@swm.pp.se