[mif] clarification on HE-MIF algorithm
GangChen <phdgang@gmail.com> Mon, 23 November 2015 09:18 UTC
Return-Path: <phdgang@gmail.com>
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 A36311A1B05 for <mif@ietfa.amsl.com>; Mon, 23 Nov 2015 01:18:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 QHTwAhwa5Ndc for <mif@ietfa.amsl.com>; Mon, 23 Nov 2015 01:18:49 -0800 (PST)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 304DF1A1B9C for <mif@ietf.org>; Mon, 23 Nov 2015 01:18:49 -0800 (PST)
Received: by iofh3 with SMTP id h3so181202399iof.3 for <mif@ietf.org>; Mon, 23 Nov 2015 01:18:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=/gD3/iY6oHvxMCWOgvmTtQ0T2fvmcUnTvL2HpSMQdzY=; b=t05IlxhCpqC4wiKXOmAbkmC6rfZ3ak/gp279D88agEZzPYp1+U7icaOTipurM1CB1b TRuuKlbHX2R/anovYZA4/N+FvBrZom+RM6Jv9jgNvyr4WFrRHrPD26l2SlD61jtGiOGv TCeQROv6flZjuGGct94H+uwq3HJC9OqZsUhEW2YOYsXrnQpUmCazOK2DY3Hud9Lfo9u8 Diiir65fIDNrzWGBg++HPtcmd7+LbGaoEdPfl9mXKwzWQAq5SQVGloguTp2nqqztWlz4 V2CWgYarMLEuaA8oYah/cVFPe1F+9k4Vj8r/AxkRvxl2XyA3/0TlHaU4m35fedasl5Un Eb8Q==
MIME-Version: 1.0
X-Received: by 10.107.137.226 with SMTP id t95mr23870520ioi.188.1448270328667; Mon, 23 Nov 2015 01:18:48 -0800 (PST)
Received: by 10.36.154.3 with HTTP; Mon, 23 Nov 2015 01:18:48 -0800 (PST)
Date: Mon, 23 Nov 2015 17:18:48 +0800
Message-ID: <CAM+vMETqmJSEdPzBUqacH8a1fMwvxeMwew1vJG5g7sxMHRfDwA@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: "mif@ietf.org" <mif@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mif/sXCvejn5x9LN-wmhdVAmlLVbYNM>
Cc: Hui Deng <denghui02@hotmail.com>, Margaret Cullen <mrcullen42@gmail.com>
Subject: [mif] clarification on HE-MIF algorithm
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 23 Nov 2015 09:18:50 -0000
wg, I would like to follow the meeting minutes to clarify a question from the discussion. " DT - Clarifying question - base happy happy eyeballs spec has two algos, none of them mandatory no mandatory algorithm Does this specify a mandatory algo? " The HE-MIF doesn't specify mandatory algorithm. Basically, HE-MIF is doing a similar way with RFC6555. The draft describes step-wise requirements for any candidate algorithm. BRs Gang 2015-11-22 8:40 GMT+08:00, Hui Deng <denghui02@hotmail.com>: > Hello all > > Appreciate Ian Farrer and Ted Lemon kindly help for minutes > Also Mikael Abrahamsson for Jabber > > https://www.ietf.org/proceedings/94/minutes/minutes-94-mif > > Please feel free to let chairs know whether you have some revision > > thanks a lot > > DENG Hui >
- [mif] clarification on HE-MIF algorithm GangChen
- Re: [mif] clarification on HE-MIF algorithm Dave Thaler
- Re: [mif] clarification on HE-MIF algorithm GangChen
- Re: [mif] clarification on HE-MIF algorithm Hui Deng