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

<yoshihiro.ohba@toshiba.co.jp> Fri, 04 July 2014 04:45 UTC

Return-Path: <yoshihiro.ohba@toshiba.co.jp>
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 934C81B2BCB for <mif@ietfa.amsl.com>; Thu, 3 Jul 2014 21:45:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.343
X-Spam-Level:
X-Spam-Status: No, score=-2.343 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 kODa7fRzjBku for <mif@ietfa.amsl.com>; Thu, 3 Jul 2014 21:45:03 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B51671A04C8 for <mif@ietf.org>; Thu, 3 Jul 2014 21:44:59 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp with ESMTP id s644ilFD025160; Fri, 4 Jul 2014 13:44:47 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp id s644il2M012210; Fri, 4 Jul 2014 13:44:47 +0900 (JST)
Received: from unknown [133.199.192.144] by arc1.toshiba.co.jp with ESMTP id PAA12209; Fri, 4 Jul 2014 13:44:47 +0900
Received: from mx11.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp with ESMTP id s644ilYF002008; Fri, 4 Jul 2014 13:44:47 +0900 (JST)
Received: from tgxml050.toshiba.local by toshiba.co.jp id s644ileF018435; Fri, 4 Jul 2014 13:44:47 +0900 (JST)
Received: from TGXML210.toshiba.local ([169.254.4.202]) by tgxml050.toshiba.local ([133.199.68.70]) with mapi id 14.03.0181.006; Fri, 4 Jul 2014 13:44:47 +0900
From: yoshihiro.ohba@toshiba.co.jp
To: swmike@swm.pp.se, fsong@bjtu.edu.cn
Thread-Topic: [mif] New draft about MIF API extension for combining IEEE 802.21
Thread-Index: AQHPlsIqGzKD4JEyD0qE+Fh0JEfiRpuPVKjg
Date: Fri, 04 Jul 2014 04:44:46 +0000
Message-ID: <674F70E5F2BE564CB06B6901FD3DD78B2724FFE3@TGXML210.toshiba.local>
References: <604109602.03243@bjtu.edu.cn> <604363291.17829@bjtu.edu.cn> <alpine.DEB.2.02.1407031517120.7929@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1407031517120.7929@uplift.swm.pp.se>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
x-originating-ip: [133.196.20.226]
msscp.transfermailtomossagent: 103
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mif/MlmhvzIjS76l4geG5zYXB7eJCrY
Cc: mrw@lilacglade.org, mif@ietf.org, denghui02@hotmail.com
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
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 04:45:05 -0000

Anyone can get IEEE 802 specifications with no cost or membership after 6 months passing from publication date from: http://standards.ieee.org/about/get/.

Yoshihiro Ohba

-----Original Message-----
From: mif [mailto:mif-bounces@ietf.org] On Behalf Of Mikael Abrahamsson
Sent: Thursday, July 3, 2014 10:25 PM
To: Fei Song
Cc: mrw; denghui02; mif
Subject: Re: [mif] New draft about MIF API extension for combining IEEE 802.21

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